FINANCIAL ACCOUNTING/CONTROLLING

I got solution for blogger templates error

sirish.sites@gmail.com (Sirish WebWorld) — Fri, 20 Feb 2009 15:00:00 +0530

Getting error on changing of Blogger/Blogspot template - bX-928o1o ?

Here's the solution:

For myself, i deleted all the left-hand side widgets/gadgets, and proceed to steps #4, I managed to have my new template!!

Here's the Step by step solution that i got it from a forum.

1. Make sure you have some sidebar elements before trying to upload the new template (this is so that you get the 'Widgets are about to be deleted warning')

2. You should now have your new template code in place (awaiting widget deletion confirmation)

3 Press cntl+f (find function) and search for 'widget' (without inverted commas)

4 Change the number 1 in the following: b:widget id="Blog1",
b:widget id="BlogArchive1" and b:widget id="Profile1" to 2.

5. Confirm and save

Hope this will be helpful to you, have a nice day :)

Multilevel Worklist

sirish.sites@gmail.com (Sirish WebWorld) — Fri, 13 Feb 2009 09:46:00 +0530

Use

The worklist of the Schedule Manager is a multilevel worklist. This worklist is particularly useful for the period-end closing activities.

Why Is the Worklist Multilevel?

In previous releases, the period-end closing process in the R/3 system consisted of a series of batch jobs. The sequence of the processing steps was established by the order in which the jobs were called. The objects were selected separately for each job. Through the selection criteria entered, it was possible to specify a unified scope of selection. This scope of selection had to be respecified for each processing step (that is, for each individual function of period-end closing).

When an object was processed, errors that occurred in previous processing steps were not taken into account. For this reason, it was necessary to check the objects that had errors once a job was completed. Any errors had to be corrected and then the job restarted for the entire scope of selection. In some areas (such as the period-end close in Product Cost by Period), it was already possible to create a single-level worklist for individual processing steps. With this single-level worklist, the objects with errors could be called up for each processing step, and the causes of the errors determined. The processing step could then be performed again for the object after the error was corrected. This worklist did not prevent objects with errors from being processed in the subsequent processing step (that is, in the subsequent job).

Advantages of the Multilevel Worklist

The worklist of the Schedule Manager is a multilevel worklist. This means that the worklist is generated for a sequence of processing steps rather than for just one processing step. The worklist therefore enables efficient execution of processing step sequences. Processes such as period-end closing can be performed much more efficiently with a multilevel worklist.

The multilevel worklist has the following advantages:

The processing step sequences (such as in period-end closing) can be performed faster than before.

Manual processing after completion of each job is no longer necessary. Manual processing is only necessary after executing a sequence of processing steps that consists of multiple jobs (for example, complete closing of an application component).

Furthermore, if errors were issued for objects in the single-level worklist, it was often necessary to repeat the processing steps for the entire scope of selection (and not just for the objects with errors). With the multilevel worklist, the processing steps are repeated only for the objects that have errors.

CPU time is reduced because objects are selected only once for each processing step sequence, instead of for each individual processing step. Objects are selected before the first processing step is executed. The multilevel worklist provides performance benefits particularly with complex structures in which dependencies between objects must be taken into account (such as complex project structures).

As a rule, jobs are planned and monitored by members of the EDP team. In many cases, these employees are not responsible for the correcting the errors shown in the error logs. With the multilevel worklist, you can directly inform the employees responsible for correcting the errors. This notification takes place by means of a mail message that is sent automatically through the workflow.

Integration

The multilevel worklist is part of the Schedule Manager and is always used with the other functions of the Schedule Manager (see Prerequisites).

The following applications, functions, and objects are currently supported by the multilevel worklist:

Cost Object Controlling: Manufacturing Orders and Product Cost Collectors

Process Flow	Period-end closing for manufacturing orders and product cost collectors
Scope of Selection for Processing Objects	Closing encompasses production orders, CO production orders (production orders without a quantity structure), process orders; product cost collectors and QM orders. With co-products, some of the period-end closing work is performed at the level of the items of the manufacturing orders. A prerequisite is that the following requirements are met for these objects: The objects are not assigned to a cost object hierarchy, or it is specified in the cost object category that the individual orders of a material are processed outside the cost object hierarchy (see Product Cost by Period). Account assignment can be made directly on the objects. This means that with regard to the selection of manufacturing orders, account assignment is made on the manufacturing orders themselves and not on a product cost collector. The objects do not have status DLFL (deletion flag). Product cost collectors are objects of the Product Cost by Period subcomponent. Manufacturing orders (including manufacturing orders without a quantity structure) are objects of the Product Cost by Order subcomponent.
Processing Step	Objects
Template allocation	Order header (including product cost collectors)
Revaluation at actual prices	Order header (including product cost collectors)
Actual overhead	Order header (including product cost collectors)
Preliminary Settlement for Co-Products, Rework	Preliminary settlement for co-products: Order header of manufacturing orders as processing objects; order items as receivers Preliminary settlement of rework: Order header of manufacturing orders as processing objects, order header of manufacturing orders or product cost collectors as receivers; but not: Settlement of rework on product cost collectors or manufacturing orders assigned to a cost object hierarchy (see below) Preliminary settlement of collective orders (old processing method without automatic goods movement) Header of manufacturing orders as processing objects, header of manufacturing orders as receivers
WIP calculation	Production and process orders or, in joint production, their items, as well as CO production orders and product cost collectors
Variance c alculation	Production and process orders or, in joint production, their items, as well as CO production orders and product cost collectors
Settlement	Production and process orders or, in joint production, their items, as well as CO production orders and product cost collectors

Cost Object Controlling: Cost Object ID (Cost Object Nodes in a Cost Object Hierarchy and General Cost Objects)

Process Flow	Period-end closing for cost object ID
Scope of Selection for Processing Objects	Period-end closing includes: Cost object nodes of cost object hierarchies and the single objects assigned to the cost object hierarchy These can be the following: Product cost collectors, manufacturing orders, production orders without quantity structure, and (if applicable) order items of manufacturing orders (with joint production) for which the following conditions apply: Account assignment can be made directly on the objects. This means that account assignment for manufacturing orders is made on the manufacturing order itself and not on a product cost collector. The objects do not have the status DLFL (deletion flag). Cost object hierarchies are part of the Product Cost by Period component. General cost objects General cost objects are objects of the Costs for Intangible Goods and Services component.
Processing Step	Objects
Template allocation	Cost object nodes of cost object hierarchies or the single objects assigned to the cost object hierarchy (product cost collectors, manufacturing orders or production orders without quantity structure); general cost objects
Revaluation at actual prices	Cost object nodes of cost object hierarchies or the single objects assigned to the cost object hierarchy; general cost objects
Actual cost distribution	Cost object nodes of cost object hierarchies; the single objects assigned to the lowest cost object nodes are the final receivers
Actual overhead	Depending on the Customizing settings, cost object nodes of cost object hierarchies or the single objects assigned to a cost object hierarchy; general cost objects
Preliminary Settlement for Co-Products, Rework	Only for orders assigned to the cost object hierarchy: Preliminary settlement for co-products: Order header of manufacturing orders as processing objects, order items as receivers Preliminary settlement of rework: Order header of manufacturing orders as processing objects, order header of manufacturing orders or product cost collectors that are assigned to the cost object hierarchy as receivers
WIP calculation	The single objects assigned to a cost object hierarchy; but not: Order items in joint production (manufacture of co-products), CO production orders
Variance calculation	Depending on Customizing settings, cost object nodes of cost object hierarchies or the single objects assigned to the cost object hierarchy
Settlement	Depending on Customizing settings, the top nodes of a cost object hierarchy or all nodes of the cost object hierarchy; if applicable, all orders assigned to the cost object hierarchy, and in joint production the items of the manufacturing orders; All general cost objects

Project System

Process Flow	Period-end closing for Project System
Scope of Selection for Processing Objects	WBS elements, networks, and orders
Processing Step	Objects
Generation of settlement rule	WBS elements
Template allocation	WBS elements, networks, and orders
Actual overhead	WBS elements, networks, and orders
Revaluation at actual prices	WBS elements, networks, and orders
Cost forecast	Networks
Interest calculation	WBS elements, networks, and orders
Project earned value	WBS elements, networks, and orders
Results analysis	WBS elements and orders
Incoming orders	WBS elements
Settlement	WBS elements, networks, and orders
Reporting	WBS elements, networks, and orders

Internal Orders

Processing Step	Period-end closing for internal orders
Scope of Selection for Processing Objects	Internal orders, maintenance orders
Processing Step	Objects
Template allocation	Internal orders, maintenance orders
Revaluation at actual prices	Internal orders, maintenance orders
Actual overhead	Internal orders, maintenance orders
Interest calculation	Internal orders, maintenance orders
Results analysis	Internal orders, maintenance orders
Settlement	Internal orders, maintenance orders

Sales Orders

Processing Step	Period-end closing for sales orders
Scope of Selection for Processing Objects	Sales order items that carry costs and revenues
Processing Step	Objects
Template allocation	Sales order items that carry costs and revenues
Revaluation at actual prices	Sales order items that carry costs and revenues
Actual overhead	Sales order items that carry costs and revenues
Results analysis	Sales order items that carry costs and revenues
Settlement	Sales order items that carry costs and revenues

Prerequisites

You are working with the Schedule Manager and are using all of its functions.

A prerequisite for the use of the multilevel worklist is that a constant quantity of objects (or, in subsequent executions, their subset) is processed in a predefined sequence of processing steps.

The selection set of the objects is determined through the application you select (for example, Cost Object Controlling: Manufacturing orders and product cost collectors) (see above), as well as through any additional entries that you may make when creating report variants (see below).

The sequence of processing steps is specified in the flow definition.

This means that you proceed as follows:

Go into the

Scheduler

of the Schedule Manager.

From the scheduler, create a

flow definition

. In the flow definition, specify the processing step sequence (for example, a sequence of all single functions of period-end closing for product cost collectors). The creation of the flow definition is realized through the Workflow Builder.

You access the flow definition with the menu options Extras ® Process the flow definition. When you create the flow definition, you should:

Specify which application the flow definition is intended for (such as Cost Object Controlling: Manufacturing Orders and Product Cost Collectors)

Make sure you create a flow definition with a worklist

The Workflow Builder appears. Depending on the application you selected, you receive a SAP template that you can modify to meet your requirements.

Create a task for each processing step in the flow definition. Such tasks can be, for example, reports for the single functions of period-end closing or user decisions.

To facilitate maintenance of the flow definition, the system offers you a default template. This consists of a task placeholder at the beginning of the flow as well as a task placeholder in the feedback loop. You define the placeholder at the beginning of the flow before the feedback loop as a report task for selecting the worklist. You define the single functions of period-end closing as tasks in the feedback loop.

To define the selection or a single function (such as overhead calculation) as a task, select the Program indicator when you create the task. Then, select the report from a proposal list that you want to include in the processing sequence (such as Overhead: Worklist of Manufacturing Orders)

Then create a report variant for the execution of the report. Maintain the parameters for the variant. Here you can specify various parameters such as whether a detail list is output and whether processing takes place simultaneously on multiple servers.

You can further filter the scope of selection of the object to be processed by using a selection profile.

In addition, enter the period and fiscal year.

You can use the same flow definition each time if you enter selection variables instead of fixed values for the period and fiscal year when you maintain the report variants. In this case, the system calculates the period and fiscal year of the single functions dynamically from the current values for these variables when it executes the flow definition. This is only possible if you use selection variables (called TVARV variables) for the period and fiscal year parameters. When you create the report variant, you specify that you are working with selection variables. You maintain the selection variables by entering the transaction STVARV, or by starting the transaction through Extras ®Settings ® Selection Variables in the menu of the Schedule Manager and changing the variables there to the period and fiscal year to be processed. This enables you to use the same job variant every month. You only need to update the TVARV variable before executing the job variant.

You specify a user decision if you want the previous processing results to be checked after one or more processing steps. After executing the previous processing steps, the system automatically sends a mail message to the person responsible for checking the results (usually the cost accountant). When you create the flow definition, you specify which user receives this mail.

When you use the multilevel worklist, the system always specifies a user decision and a feedback loop for the reentry into postprocessing as the last step of the flow definition.

You can also insert user interactions at other points in the process definition if you want to check the objects processed up to a particular step before continuing with processing.

If you approve (release) the check of the objects with errors, you make it possible for the objects with errors to automatically be reprocessed later.

Enter the flow definition as a task in the task list of the Scheduler.

Start the task (the flow definition) in the Scheduler.

You monitor the flows and jobs during and after processing in the

monitor

of the Schedule Manager.

Features

Basic Functions of the Multilevel Worklist

The multilevel worklist is generated for an entire sequence of processing steps.

The scope of selection is determined once and is valid for all processing steps. The worklist encompasses the objects of the scope of selection for which processing in the present processing step sequence is both possible and necessary. The scope of selection, therefore, equals the maximum scope of the worklist. Certain restrictions can be specified for individual processing steps in the scope of selection. These restrictions are usually determined through selection profiles that are specified when report variants are created.

The processing steps are performed in an order strictly defined in the flow control of the scheduler. A processing status is maintained for each object and processing step. The processing status indicates whether further processing of the object is allowed.

Each processing step only contains the objects for which (based on the processing status of the previous processing step) processing in this step is allowed.

In each processing step, dependencies between objects are interpreted according to the application. For this reason, it can be necessary to include other objects when processing an object in a step. The system accounts for such object dependencies automatically. You do not have to make any additional settings.

You want to perform results analysis for a WBS element (nonvaluated project stock). Production orders whose actual costs should be included in results analysis are assigned to the WBS element.

There are individual worklists for each processing step sequence (that is, each flow definition). Typical processing step sequences are the period-end closing sequences for the individual application components. Individual worklists are created for each application (for example, for internal orders and projects).

The multilevel worklist fulfills the following basic requirements:

The selected objects are processed as far as possible.

The selected objects are only processed when processing is both necessary and possible.

Object dependencies are taken into account.

Object dependencies can be encountered, for example:

In engineer-to-order environments

When you are using cost object hierarchies

Suppose you are performing results analysis for WBS elements in an engineer-to-order environment. The system first determines which WBS elements are relevant on the basis of the selection criteria. These WBS elements are called primary objects because they are the original objects to be processed.

Results analysis also includes values that are posted to the production orders assigned to the WBS elements. These production orders are selected on the basis of their dependency on the WBS element. They are called secondary objects.

The determination of secondary objects depends not only on the type of worklist (for example, cost object hierarchies, projects), but also on the present business function and on the processed objects.

Suppose you are performing period-end closing for a cost object hierarchy.

You calculate the actual overhead at the level of the cost object nodes. In this case, there are no dependent objects because every cost object node is included in overhead calculation. Relationships to other cost object nodes do not play a role.

You also want to distribute the actual costs assigned to the cost object nodes to the lowest cost object nodes of the assigned product cost collector. The following situation arises during distribution:

As soon as a cost object node in a cost object hierarchy is a primary object, all other nodes are secondary objects (as long as they are not also primary objects).

During the execution of the flow definition, the individual processing steps receive a list of the objects to be processed. Each processing step sends the processing status of each object and a list of the displayed messages back to the worklist.

The scope of selection can contain all objects to be processed in a particular flow. However, in some situations you may want to perform the same flow more than once in parallel with different scopes of selection. This manual parallel processing can serve to reduce the overall run time.

Suppose you want to perform period-end closing for the application component Product Cost by Order in Cost Object Controlling. You can process all production orders and process orders in a plant, or all plants in a controlling area.

You create multiple scopes of selection in which you select by plant and order type. This means that, for example, one scope of selection includes all production orders in a plant, while another scope of selection includes all process orders in that same plant.

The previous processing step in the sequence must be fully completed before the next step can be started.

After the entire processing step sequence has been executed, the user forces a manual check.

The user-defined flow of individual processing steps (specified in the flow definition), the check of the objects with errors, as well as the release of this check (for renewed processing of objects) should be repeated until all objects in all processing steps have the status OK. Once this is achieved, processing is completed.

Processing of Objects in the Worklist

You process the worklist in the monitor. The monitor shows a list of the faulty objects and the messages issued for the objects. This information is needed for analyzing and correcting the errors.

In the monitor, you can specify how objects are to be processed the next time the processing step sequence is executed. For example, you can specify the following:

That objects marked as faulty in a given processing step are excluded the next time that processing step is executed, and instead enter the subsequent processing step.
That objects processed without errors are nevertheless reprocessed if they are faulty in a business sense (for example, as a result of incorrect Customizing settings)

If an object was processed without error in an update run for project interest calculation, new interest calculation can only be triggered if the previous interest calculation is first reversed. If no reversal is carried out, the object is not included in the recalculation of interest even though its processing status would normally allow this.

You control this through the processing status for the object and processing step.

Note the following:

If an object has been changed since it was processed in the processing step sequence defined by the flow definition (for example, additional costs have been assigned to the object), this change is not taken into account if the object has already been processed without error. In this case, you should change the processing status for the first processing step of the processing step sequence to force reprocessing.

See also:

See the following sections for additional information on the monitor and how to use it:

Schedule Manager: Monitor - Working with the Object List

Processing Worklists

Processing Status

Triggering Reprocessing of Objects

Automatic Reprocessing

Once all objects have been processed and you have corrected the errors or specified that the processing step for which errors were issued should be skipped, the processing step sequence can be repeated in order to reprocess the objects that had been faulty in the previous run. You initiate reprocessing from the mail.

The system then processes the objects in the selection scope that had been processed with errors in the first run of the processing sequence and those that you instructed the system to reprocess (processing forced manually). For each object, processing starts with the processing step that had errors or for which processing was forced manually. The only processing steps repeated for an object are those for which errors occurred in the previous run, those that have not yet been performed, and those for which reprocessing was forced.

Both in the first run and in the repeated run, the only objects that are processed in each processing step are those that were successfully processed in the previous step and that have not yet been successfully processed in the current step. This limits the number of objects to be reprocessed in each step to those for which errors appeared in that step or in the preceding steps of the first run. Dependencies between objects are also taken into account. That is, depending on the object to be processed and the processing step, it may be necessary to reprocess additional objects even though they were already processed successfully.

Administrative Data Reorganization of the Multilevel Worklist

The administrative data of multilevel worklists encompasses the scope of selection, the step information (flow step), the processing status for the object, and the error messages for the object. This administrative data is deleted together with the workflow data of the Schedule Manager. It is not possible to archive the worklists.

Activities

Once all processing steps have been executed, the system informs you by mail that the results of the processing steps are ready for review. After you have checked the results and corrected any errors, the system asks you whether you would like to repeat reprocessing.

To make the relevant checks, access the monitor of the Schedule Manager.

You can access the monitor in the following ways:

From the mail
Directly from the menu of the application component

See also:

Multilevel Worklist: Process Flow

sirish.sites@gmail.com (Sirish WebWorld) — Fri, 13 Feb 2009 09:44:00 +0530

Prerequisites

You have created a flow definition. In the flow definition, you define the sequence of processing steps that you want to perform. A processing step corresponds to a single function. Examples of individual processing steps are WIP calculation, variance calculation, and settlement. A processing step sequence is defined by linking these single functions to each other in a flow definition.

You have established the flow definition in the scheduler.

Process Flow

The system starts the sequence of processing steps in accordance with the planning specified in the scheduler. The objects to be processed are selected on the basis of the following logic:

Objects that were processed successfully in the previous flow step but have not yet been processed successfully in the current flow step are transferred from the selection to be processed. These objects are called primary objects.

The system also reads the dependent objects for the current flow step for all selected objects. These dependent objects are called secondary objects. If a primary object has one or more secondary objects that were not successfully processed in the previous flow step, neither the primary object nor its associated secondary objects can be processed in the current flow step.

The system executes the processing steps.

When the system has executed all processing steps, you receive a mail to inform you that the planned sequence of processing steps has been completed. This mail is generated using the workflow link.

You can reprocess the faulty objects directly from the mail.

The user can view the processed objects with their processing status in the monitor of the Schedule Manager.

The user processes the objects with errors.

The user retriggers the processing step sequence from the mail in his office inbox.

The system now processes the objects in the selection that were processed with errors in the first run of the processing sequence, or whose processing was forced manually.

For each object, processing starts with the step that was not processed correctly.

The subsequent processing steps are then started automatically in the defined sequence.

If an object that was processed without errors in the first run of the processing step sequence is changed before the second run of the processing step sequence, these changes do not result in an automatic reprocessing of the object. If you want the object to be reprocessed, manually set the corresponding processing status.

The production order 1000000 is included with all other production orders of plant 1000 in period-end closing of Product Cost by Order. Work in process for the order is calculated as EUR 1,000 and settled to Financial Accounting (FI). All processing steps (for example, WIP calculation and settlement) of the processing step sequence were also performed without out errors.

However, not all production orders were processed without errors. In this way, for example, the production order 1000005 receives the processing status error for the processing step WIP calculation and the production order 1000010 receives the processsing status error for the processing step Settlement.

After work in process has been settled for all production orders, including production order 1000000, additional costs amounting to EUR 200 are posted to production order 1000000.

Remove the errors for the production orders 1000005 and 1000010 and reinitiate the processing step sequence. The production orders 1000005 and 1000010 are reprocessed. Production order 1000000 is not processed as it was processed without errors in the first run.

If you want to force a reprocessing of production order 1000000, you can manually set the corresponding processing status.

See also:

Schedule Manager: Worklist

Schedule Manager: Monitor - Working with the Object List

Processing Status of Objects and Processing Steps

Processing Worklists

Monitor - Working with the Object List

sirish.sites@gmail.com (Sirish WebWorld) — Fri, 13 Feb 2009 09:43:00 +0530

Definition

The monitor of the Schedule Manager is a tool for processing multilevel worklists. It contains information on active or completed jobs that were planned in the scheduler.

Use

This section provides information on using the object list in the monitor of the Schedule Manager.

For more information on jobs in the monitor, see Using the Monitor.

The monitor performs the following functions:

Displays the available worklists and their processing steps

Keeps track of the processing status of each object (such as product cost collectors, WBS elements, internal orders, and production orders) and each processing step

Assists you in analyzing the causes of errors for the objects and processing steps

Displays the processing status of objects (particularly for the objects with errors)

Shows the hierarchical relationships between the objects

Compares object hierarchies with each other

Controls whether objects enter the next processing step

Sends objects to the responsible person for further processing

You can set the processing status so that objects of negligible value, for example, are not reprocessed in a processing step even if errors are issued for the objects in that step. In this case, it is not necessary to remove the cause of the error.

Structure

The monitor is divided into the following screen areas:

Structure Tree with Worklists/Processing Steps/Jobs

The structure tree containing the worklists, processing steps and jobs is displayed on the left side of the monitor.

In the system, the worklists are updated separately for each scope of selection and processing step sequence. The processing step sequence is specified in the flow definition. You can view the worklists of the application component in which you are working, including their functions and objects.

The system displays the following information on each worklist:

Number of objects in the worklist
Processing steps
Number of objects processed in each processing step
Number of objects with errors in each processing step

Object List

The object list is located in the top right area of the screen. The object list can display one or more processing steps of a worklist. You select the processing steps in a worklist in the structure tree worklists/processing steps/jobs.

The object list includes the following information:

The objects for the selected processing steps. You can control which objects are displayed for each processing step by means of a filter that takes the individual processing statuses into account. In application toolbar icons for object list, choose the icon Objects: Set status filter
The system uses the last user-specific default setting of the dialog box. Note the default settings of this dialog window in the SAP standard system. The last user-specific setting of the dialog box is the default.
The processing step performed for the object
The processing status of the object for each processing step
A check box you can select to indicate that you have processed the object in the worklist monitor
The person responsible for the object (if any)

Message List

The message list is located in the lower right-hand portion of the screen. The message list displays messages for certain objects. You can use these messages to analyze the causes of error for each object and processing step.

See also:

Schedule Manager: Multilevel Worklist

Multilevel Worklist: Process Flow

For detailed information on using the monitor of the Schedule Manager, see the following section:

Processing Status of Objects and Processing Steps

Processing Worklists

sirish.sites@gmail.com (Sirish WebWorld) — Fri, 13 Feb 2009 09:40:00 +0530

Use

You process worklists in the monitor of the Schedule Manager.

Navigating to the Monitor

Procedure

You can access the monitor in the following ways:

In the Schedule Manager, there are three ways of accessing the monitor from the screen Schedule Tasks for Task List: By selecting a calendar day, selecting the desired tasks in the daily overview, and then choosing Monitor daily overview in the application toolbar; by choosing the Monitor icon above the daily overview; or by double-clicking on a task in the daily overview.

From the menu of the application component. For example, to access the worklists of the Product Cost by Period component, go to the menu of Product Cost by Period and choose Period-End Closing ® Schedule Manager ® Worklist Monitor. Choose the following: Product Cost Collector or Cost Object Hierarchy. The screen Select Worklist appears.
In the selection screen, use the possible entries function for the Application field to select the application component for which you want to call up the worklist (such as Cost Object Controlling: Manufacturing Orders and Product Cost Collectors). Usually the appropriate application will already be shown as a default. Enter the additional selection criteria such as the period and fiscal year, and choose Enter. You can further restrict the selection with the icon Further selection criteria.

Result

The screen Schedule Manager: Monitor appears.

Working with the Monitor of the Schedule Manager

Using the Monitor

The monitor enables you to analyze the objects processed in a worklist and control how the objects are processed further. The focus is on the objects for which errors were issued.

Objects for which errors were issued in a processing step do not enter the next processing step.

You can analyze and correct the error, or you can instruct the system to skip processing (that is, not to process the objects in the corresponding step). Skipping processing can be appropriate for objects that have errors but whose value is negligible.

You instruct the system to skip processing by setting the processing status to skip processing. The system then processes the object in the next processing step as if it had been processed without errors in the previous step.

If the object is part of a hierarchy, this can also prevent the object from stopping the entire hierarchy from being processed.

The functions hierarchy display and hierarchy comparison provide support when you search for errors.

When actual overhead rates were calculated in the period-end closing process, one production order was not processed due to faulty Customizing settings. The production order is assigned to a WBS element. When the cost accountant reviewed the objects in the monitor, he decided that the missing overhead is insignificant and can be disregarded, since the effort involved in finding and correcting the error would be out of proportion to the amount in question. The faulty production order should therefore be included in results analysis for the WBS element. To prevent the entire project to which the production order is assigned from being excluded from processing, the accountant sets the processing status of the production order for the step overhead to Skip processing.

On the other hand, it may sometimes be necessary to process an object again even though it has been processed without error. You do this by setting the status Repeat processing. This can be appropriate in cases where incorrect Customizing settings have resulted in improper values. The processing steps only recognize errors that are indicated as errors in the monitor. However, an object can be faulty in a business sense without necessarily generating an error message.

Such errors can only be found by checking the results by hand.

In the flow definition, you can specify that a manual check (usually by the cost accountant) should take place after certain processing steps.

To force renewed processing of the object after correcting the error (in our example, this would involve selecting another results analysis method in Customizing), you change the processing status to Repeat processing.

Suppose you want to calculate results analysis data for a WBS element. In Customizing, you selected a results analysis method that causes unrealized profits to flow into inventory valuation. However, you don’t want unrealized profits to be inventoried.

It may also be necessary to force an object to be processed due to the fact that postings which debited an object after period-end closing made the period-end closing data obsolete.

Suppose you have performed period-end closing for a production order. All processing steps of the production order were performed without error. The production order is then debited with additional costs that must be accounted for in period-end closing. You must therefore force the system to repeat the processing steps for the production order. In this case, you only need to force a repeat of the first processing step of the sequence. The production order is automatically included in all subsequent processing steps.

The monitor of the Schedule Manager is divided into three screen areas:

Structure tree with worklists/processing steps/jobs

Object list

Message list (you have the choice between object messages, step messages, and messages of the originating objects)

Structure of the Monitor

Different functions are available in each screen area. These functions are described in the Procedure section below.

Procedure

Displaying Objects for One or More Processing Steps

You want to view the processed objects for one or more processing steps.

In the object list, you can choose to view all processed objects or only the objects with errors, for example, for one or more processing steps. Since the worklist’s primary function is to assist you in analyzing the objects with errors, you should limit yourself to viewing only the objects that have errors. If you choose to view all processed objects, this will reduce system performance.

With the default settings of the standard system, objects with the following processing statuses are displayed:

Flagged for postprocessing

Processing forced manually

Error

Followup error

Hierarchy error

Minor error

For detailed information on the processing statuses updated for the objects, see the following section: Processing Status for Objects.

To view the objects, proceed as follows in the structure tree worklists/processing steps/jobs:

Double-click on a processing step in the structure tree with worklists/processing steps/jobs to generate the object list for that processing step. If there are any messages that refer to the processing step as a whole (rather than to specific objects), they are displayed in the message list.

Double-click on a worklist in the structure tree with worklists/processing steps/jobs to generate the object list for all processing steps. If there are any messages for the worklist, they are shown in the message list.

You can also select the processing steps with the context menu. Proceed as follows:

a) To display all processing steps for the objects in a worklist:

Select a worklist with the right mouse button and choose Object list - All steps in the context menu. The object list for the worklist is generated.

The object list can display up to ten processing steps. If there are more than ten steps, the dialog box Select Processing Steps appears, in which you can select a maximum of ten steps.

a) To display individual processing steps for the objects in a worklist:

If you don’t want to see all processing steps for a worklist, select a worklist with the right mouse button and choose Object list - Select steps in the context menu. The dialog box Select Processing Steps appears, in which you can select a maximum of ten steps.

When you process worklists for manufacturing orders, the object list has a column for the material number. The material shown in this column is usually the material that is manufactured with the order shown in that row.

In joint production, the column shows the following:

For the order header (i.e., for the object "ORD order"):

If a process material is being used, the process material is shown.

Otherwise the leading co-product is shown. The leading co-product is the co-product shown in the first order item.

For the order item (i.e., for the object "OIT order item"), the material produced with that order item is shown.

Displaying the Processing Status for Each Object and Processing Step

The object list shows the processing status for each object and processing step. A column is displayed in the object list for each processing step selected in the structure tree worklists/processing steps/jobs. This column shows the processing status of each object. The processing statuses are represented as icons. If you want to know which processing status is assigned to which icon, then click on the corresponding Legend icon above the object list. The screen Processing Status: Icon Legend appears. The icon in the dialog box provides explanations of the processing statuses.

For detailed information on processing statuses, including examples, see the following section: Processing Status for Objects

Filtering Objects

You can also display objects of other processing statuses through a status filter. To do so, click on the filter icon (Objects: Set status filter) above the object list. Select the relevant processing status and press Enter. All objects that have the corresponding processing status are displayed in the object list.

You can also filter objects according to criteria other than the processing status (function of the ABAP List Viewer).

Deciding Whether to Process Objects Further

You now have a list of objects. These are normally the objects with errors. You must decide whether to continue processing these objects. You have the following options:

You correct the errors.
You instruct the system to continue processing the objects even though you have not corrected the errors. This is appropriate for objects whose value is insignificant.

Reports on the objects are available to help you reach a decision.

Executing Reports

Reports can help you determine the following:

Whether the value of the object is negligible

In this case, you instruct the system not to process the object. Otherwise, you correct the error.

Whether the values calculated for an object are acceptable in a business sense. You may also want to do this for objects that were processed without error (processing status OK).

If this is not the case, then once you have corrected the problem (the error may have been caused by faulty Customizing settings), you can force further processing. You can also assign further reports with the function report assignment (if supported).

To view a report on an object, position the cursor on the object in the object list and click on the Execute report icon above the object list. Then enter the required parameters and select the report you want to see (only for projects; production orders do not allow reports to be selected). On the basis of the data in the report, you can now decide how the object is to be handled.

To analyze the error for the objects with the processing status Error, look at the messages for the object and processing step.

Messages for One or More Objects

To see the messages that were issued for one or more objects:

1. Select the objects.

In the object list, select an object by positioning the cursor on the object, holding down the left mouse button, and pressing the Ctrl key on the keyboard. Continue to select further objects in the same way.

2. View the messages.

To see the messages for the selected objects, click the Display object messages icon above the object list. You can also display the messages for one line of the object list by double-clicking on the line.

In the pull-down menu of the Display object messages icon above the object list, you can choose between the following types of messages:

Object messages

Step messages

Messages of originating objects

The object messages appear in the message list.

3. View the long text of the messages.

To analyze the error, you will normally need to look at the long text of the message. To see the long text, double-click on the message in the message list.

Step-Specific Messages (Messages Without Reference to a Specific Object)

To see the messages for a particular processing step, go to the object list and choose the drop-down menu of the Display object messages icon, and then choose Display step messages. The step-specific messages are displayed in the message list.

Messages of Originating Objects

You should look at the messages of the originating objects particularly when you want to analyze objects with the processing status Followup error.

Skipping Processing Manually

You have decided to have the system skip a processing step for one or more objects.

In the object list, select the step statuses that you want to change. Click the icon Set processing status.

If you select the status Skip processing, the system changes the processing status to Skipped manually. The object is not included in this processing step during the next execution of the processing step sequence. The object enters the subsequent processing step as if it had been processed without errors.

Forcing Processing Manually

There are two ways to force the system to reprocess objects:

Position your cursor in the object list and press the right mouse button. In the context menu, choose Repeat processing. The system changes the processing status to Postprocessing forced manually. The next time the processing step sequence is performed, the object is included in that processing step and in all subsequent processing steps.

You can also force the system to process objects by selecting the objects and clicking the icon Set processing status (icon in the object list) and choosing Repeat processing. You can select multiple objects at the same time with the following methods:

To select an entire column, click on the column header.
To select individual columns, lines, or cells, hold down the Ctrl key and click.

The system changes the processing status to Postprocessing forced manually. The next time the processing step sequence is performed, the object is included in that processing step and in all subsequent processing steps.

Editing Master Data

From the object list, you can access master data maintenance for the object. To do so, position your cursor on the relevant object and click on the Edit master data icon above the object list. The system starts a new session. You are now in the change mode of the relevant object. You can close the session by going back (green arrow).

The error message Maintain the settlement rule of the sender is issued for a production order for the processing step Settlement. To maintain the settlement rule, call up the production order.

Display as Hierarchy

In the hierarchy view, the objects are displayed according to their hierarchical relationship to each other.

Select one or more objects in the object list and choose Display as hierarchy. The screen Object list - hierarchy view appears. In the hierarchy view, the object or objects you branched from are selected.

Expand the object hierarchy. This provides a quick overview of the relationships between the faulty objects. You can process objects to which a particularly large number of faulty objects are assigned.

To go back to the object list from the hierarchy, choose Back to object list.

In the object list hierarchy view screen, you can only change the processing status of individual objects. Mass changes to the processing status of the objects is only possible in the object list.

In addition, a requirement for the display hierarchy function is that the objects have hierarchy information in the worklist. This is the case in the Project System and for cost object hierarchies.

Hierarchy Comparison

Objects that have hierarchy information (such as projects and cost object hierarchies) can be compared with each other using the hierarchy comparison function. This allows you to more efficiently find errors that are due to differences in the values of two periods. Comparing the data of two periods is particularly useful because the items and values of the objects in the hierarchy can change between periods.

In the project system, it is also possible to compare two versions of an original structure. The changes that were made to the version are shown in a separate window.

Before you start the comparison, you specify which two data structures you want to compare. You define one of the two structures as the original structure and the other as the version. During the comparison, the two structures are represented in the form of a hierarchical structure tree in a separate screen area. You can compare individual objects, subhierarchies, or the two complete structures. The results of the comparison are grouped into different categories:

New objects (which objects were added to the version?)

Changed objects (which object attributes were changed, and how?)

Nonexistent objects (which objects do not exist or were deleted?)

Hierarchy position of changed objects (which objects changed their position in the hierarchy?)

For detailed information on the hierarchy comparison, see the documentation under:

Logistics ® Project System ® Collaborative Engineering and Project Management ® Monitoring ® Comparing Two Folders

The Schedule Manager only supports the comparison function; synchronization is not possible.

Sending Objects

Select one or more objects in the object list and choose the Send icon above the object list. To receive a log of the transmission, choose Send log. If you choose Send to agent, the person responsible for the object receives a mail in his or her inbox (Office ® Workplace ® Inbox) with information on the required change. From this mail, you can access the screen Schedule Manager: Monitor which displays only the sent objects. Note that the filter function in the icons of the object list (Objects: Set Status Filter) is not available when you access the monitor through your office inbox.

To be able to use the function for sending objects, the following settings must be made in each client:

Choose Tools ® Business Workflow ® Development ® Definition Tools ® Tasks/Task Groups ® Change.

Select task type Workflow template and enter task 20001060 (SCMA_WL_DISP). The screen Workflow Template: Change appears.

Select the tab Triggering events. Activate the event linkage by clicking the icon Event linkage active in the first column. The light symbol changes to green.

Save the data.

If no agent can be determined for the object, the dialog box Entry of Responsible Agent appears, in which you can specify the user responsible for further processing.

The object list contains the field Agent ID next to the existing column headers. This field shows the agent responsible for the object. The agent can be an R/3 user or a node in the organization plan.

On the basis of the organizational data of the objects (such as the plant, company code, and so on), you can specify criteria for each object type that are used to determine the agent.

You specify the agents responsible for the objects under:

Schedule Manager ® Extras ® Settings for worklist ® Maintain responsibilities for objects.

For detailed information on maintaining responsibilities, refer to the SAP Library under:

Human Resources ® Personnel Management ® Organizational Management ® Integration with SAP Business Workflow ® Role Resolution ® Role Definition ® Define Roles Using Responsibilities

Define Roles Using Responsibilities

Flagging Checked Objects

You can flag objects to indicate that you have checked them.

To do this, either select the check box Object checked directly, or select one or more objects and click the icon Change "checked" indicators and then in the pull-down menu:

Select indicators: selects the check boxes for the selected objects
Deselect indicators: deselects the check boxes for the selected objects
Toggle checked <-> not checked: Toggles the status for the selected objects

The indicators are only visual and have no effect on processing.

Displaying Other Worklists

To display other worklists, click the Other worklist icon at the top of the screen. The enter the required data and choose Enter. This function is only available when you access the Schedule Manager through the application components. When you access the Schedule Manager through a mail in your Office inbox, this function is not available.

Triggering Reprocessing of the Worklist

Prerequisites

Before you trigger reprocessing of the worklist, you must have done the following:

Corrected the errors of the faulty objects, or instructed the system to skip processing for those objects
Forced reprocessing of objects that are faulty in a business sense

Procedure

To trigger reprocessing, access the mail that was sent to you through the workflow. Start reprocessing from this mail.

Result

The following objects are processed:

Objects that had errors in the previous execution of the processing step sequence and whose errors have been corrected

These objects are processed starting with the processing step in which the error occurred.

Objects that had errors in the previous execution of the processing step sequence and for which the processing status Skip processing was set

These objects are processed starting with the processing step following the processing step for which the status Skip processing was set.

Objects that received the status Postprocessing forced manually

These objects are processed starting with the processing step for which the status Postprocessing forced manually was set.

See also:

Many of the icons displayed above the individual screen areas support the standard functions of the ABAP List Viewer (ALV). These icons are not explicitly explained here. The same applies to the standard ALV functions in the context menu (right mouse button). For information on the ALV, refer to the SAP Library under Cross-Application Components (CA) -> General Application Functions -> ABAP List Viewer, or under: Functions of the ABAP List Viewer

Choosing Objects for Processing

sirish.sites@gmail.com (Sirish WebWorld) — Fri, 13 Feb 2009 09:40:00 +0530

Use

An advantage of this worklist is that the objects for processing only have to be selected once per flow definition.

Prerequisites

You are in flow definition in Schedule Manager (Extras ® Flow definition ® Edit flow definition).

Procedure

Choose a processing step in the navigation area.
On the right of the screen, you see Flow definition: Task details.

Enter a new variant for this processing step and define a name for this new variant in the Variant field .

Choose Create variant.
The Variant Maintenance screen appears. Program , variant .
Here you can determine the scope of selection of the program variants for the flow definition.

To be able to choose more extensive selection criteria, first complete the required entry fields, for example Period <

006

>, Fiscal year <

2000

You can now define further selection parameters using the various pushbuttons that are offered in dialog boxes.

Choose Attributes.
The ABAP: Save Attributes of Variant screen appears.

Processing Status of Objects

sirish.sites@gmail.com (Sirish WebWorld) — Fri, 13 Feb 2009 09:38:00 +0530

Use

The processing status of an object tells you whether processing was successful in a specific processing step.

For every object listed in the worklist of the Schedule Manager, a processing status is indicated for each processing step. The system sets the processing status during processing. This status can be changed manually in the monitor.

In addition to information on the success of processing, the processing status shows whether further processing of an object is allowed. This ensures that an object which was not processed in a processing step due to errors is not passed on to the next step.

Integration

The processing status is displayed in the monitor. The status is not updated to the processed object. For more information on the monitor, see the following section: Schedule Manager: Monitor - Working with the Object List

The examples described below are based on the use of the multilevel worklist in Cost Object Controlling and the Project System.

Features

Through the processing status, the worklist of the Schedule Manager controls whether an object is processed in the following processing step. The system automatically sets the following processing statuses:

Automatic Processing Statuses

Not processed

The object has not been processed yet.

The object was processed without errors.

Minor error

A warning or error occurred while the object was being processed. However, this error does not prevent further processing in a following step.

Flagged for postprocessing

This status is set in the following case:

The object must be processed in a processing step because, for example, processing was forced. In the subsequent processing step, the object has one of the following processing statuses:

Not relevant

Minor error

Filtered

Since the object normally would not be processed when it has this processing status, the system sets the processing status of the subsequent processing step to Flagged for postprocessing. This ensures that an object processed in one step is always included in the subsequent processing steps. The processing status is reset to Flagged for postprocessing regardless of whether the object was changed in the previous processing step.

Error

An error occurred while the object was being processed that prevents further processing. You can either correct the error or instruct the system to include the object in the subsequent processing step despite the error (processing status Processing skipped manually).

Followup error

An object receives the processing status Followup error for a processing step if it belongs to a group of objects that are processed together and this group contains one or more objects that were processed with errors (processing status Error), or were not processed, in the previous processing step.

The object with the processing status Followup error is not processed in the processing step for which it received that error. This ensures that the entire group of objects can only be processed when none of the objects contains an error that hinders the processing of an object in the group.

See the end of this text for an example of the processing statuses Followup error and Hierarchy error.

Hierarchy error

An object receives the processing status Hierarchy error for a processing step if it belongs to a group of objects that are to be processed together and this group contains one or more objects that were processed with errors in the current processing step (processing status Error).

The object with the processing status Hierarchy error is not processed in the processing step for which it received that error. This ensures that the entire group of objects can only be processed when none of the objects contains an error that affects processing.

See the end of this text for an example of the processing statuses Followup error and Hierarchy error.

Filtered

The user has excluded the object from processing by defining an application-specific filter.

Not relevant

The object is not relevant for processing in this processing step due to its attributes derived from Customizing or master data.

The object is not relevant due to a status that has been set for it.

Example 1:

According to the selection parameters, all production orders of a plant are selected for variance calculation in period-end closing of Product Cost by Order. No variance key has been specified for some of the production orders. These production orders are not included in variance calculation. The production orders receive the processing status Not relevant.

Example 2:

According to the selection parameters, all production orders of a plant are selected for overhead calculation in period-end closing of Product Cost by Order. A system status or user status is set for some production orders, which does not allow processing. Examples of this are the system statuses open, closed, deletion flag and locked.

In some cases, a given status may make an object relevant or irrelevant only in certain processing steps.

Example:

A production order has a settlement rule with the settlement type FUL (full settlement). If neither the status DLV (delivered) nor the status TECO (technically completed) is set for the object, it is not relevant for variance calculation and receives the corresponding processing status. The order is relevant for the other processing steps of period-end closing such as template allocation, overhead calculation, calculation of work in process and settlement, regardless of whether one or none of the two statuses is set.

As a rule, with the processing status not relevant, no messages are issued for the object and processing step. To see the messages that caused the processing status to be set to not relevant, you can have the system process the object individually. Possibly, you can also force the issuance of messages through user-defined error management by putting the message type at the top.

For WIP calculation and results analysis, you can force the system to issue messages despite the status not relevant. You can guarantee the issuance of messages by setting the indicator Log information messages. If the indicator is set, all information messages are issued including those from processing within and outside of the multilevel worklist, even if the status not relevant is set for an object and processing step.

Manual Processing Statuses

You can set the following processing steps manually:

Processing skipped manually

In the object list, the user manually sets the processing status of an object and processing step to Skip processing. The system changes the processing status to Processing skipped manually.

The object with this processing status is not included in the relevant processing step, and enters the next processing step.

Processing forced manually

In the object monitor, the user manually sets the processing status of an object and processing step to Repeat processing. The system changes the processing status to Processing forced manually. The object is processed in the relevant processing step again even if the processing step had been executed without error.

Example

Example of the processing statuses Follow-up error and Hierarchy error:

During the calculation of actual overhead rates in period-end closing, a production order assigned to a WBS element was not processed due to deficient Customizing settings. The production order receives the processing status Error for the processing step Actual overhead.

In addition to this production order, other production orders are also assigned to the WBS element. All other production orders assigned to the WBS element receive the processing status Hierarchy error for the processing step Actual overhead. This status indicates that an object of an object group (all production orders assigned to a WBS element) contained errors in the processing step.

The processing step following the processing step Actual overhead is Results analysis. During results analysis for the WBS element, the data is included that was updated to the production orders assigned to the WBS element. Because one of the production orders assigned to the WBS element was marked as faulty and all other production orders received the corresponding processing status Hierarchy error in the processing step Actual overhead, the processing step Results analysis can not be carried out successfully for the WBS element.

The WBS element receives the processing status Followup error for the processing step Results analysis.

If you decide that the deficit resulting from the missing overhead is so low that it can be ignored, you can avoid time-consuming error analysis by specifying a processing status that prevents the production order from being included in the calculation of overhead. All production orders, including the one for which no overhead was calculated, are included in results analysis.

If the value of the production order is significant, you must remove the cause of error.

Additional Information

Note the following:

There is no one-to-one assignment of message types to processing statuses in the worklist of the Schedule Manager. For example, not every message of message type "E" (error) results in the processing status Error for an object in the Schedule Manager in that processing step.

The system issues the message CK 214 as an error message.

If this message is based on target cost version 0 in variance calculation, the processing status Error is set in the worklist of the Schedule Manager.

If this message is based on a target cost version in variance calculation that is not 0, the processing status Minor error is set in the worklist of the Schedule Manager.

Some messages are issued with different message types based on the object to be processed. Different processing statuses are set in the Schedule Manager.

In variance calculation, if message KV 158 is based on a single production order, the system issues this message as an error message. The processing status Error is set in the worklist of the Schedule Manager.

In variance calculation, if this message is based on a product cost collector to which multiple production orders are assigned, the system issues a warning message. The processing status OK is set in the worklist of the Schedule Manager.

Note the following :

If you are using the multilevel worklist of the Schedule Manager, the objects with the processing status Error for a processing step are not processed in the subsequent step. In many cases, the processing status Error is set because a message was issued with the message type "E" (error). When calculating variances and scrap variances, you can use user-defined error management to influence the message type for a large number of messages In the worklist of the Schedule Manager, this can result in a different processing status being updated to the processing step. This enables you to ensure that objects are processed in the subsequent processing step, for example.

A message was issued as an error message in variance calculation. The processing status Error is issued in the monitor.

The error is not serious, so you decide that the object should be processed in the next processing step. You therefore use user-defined error management to specify a message type of lower severity (such as "W" for a warning message). This ensures that the object does not receive the processing status Error for the processing step in the worklist due to this message. The object then enters the subsequent processing step.

No Processing Status Output

It may occasionally happen that no processing statuses are issued. See the following for an example of this: Separation of Value Calculation from Goods Movements: Effects on Cost Object Controlling.

See also:

For information on the following topics and many others, see the section Processing Worklists:

When processing should be skipped or forced manually

How to decide whether to do so

How you can change the processing status

For detailed information on user-defined error management, see the following section:

Using the Monitor

sirish.sites@gmail.com (Sirish WebWorld) — Fri, 13 Feb 2009 09:37:00 +0530

Use

The monitor shows the information on an active or completed job that was scheduled in the scheduler.

To improve performance and facilitate error rectification, use the multilevel worklist.

Integration

The monitor is part of the Schedule Manager.

Other components are:

Flow definition

You can group tasks that are to be executed in the background in a particular order (and which are controlled by the workflow) into a flow definition.

Scheduler

You can create individual tasks for business transactions (which for example, make up period-end closing) in the scheduler task list. By scheduling them in the daily overview, you enable the system to execute them.

Structure

For detailed information on the functions of the monitor, refer to:

Monitor - Monitoring Active and Completed Jobs

Monitor - Working with the Object List

Monitor - Monitoring Active and Completed Jobs

sirish.sites@gmail.com (Sirish WebWorld) — Fri, 13 Feb 2009 09:36:00 +0530

Definition

The monitor shows the information on an active or completed job that was scheduled in the scheduler.

Prerequisites

To enable the system to start jobs or job chains, you need to schedule them in the daily overview of the scheduler.

Features

To determine the current status of jobs that are still running, you can repeat the database selection.

If you only wish to see jobs with a certain status, you can hide the other statuses.

The monitor is divided into three areas:

Structure

Structure tree

The structure tree displays the workflows (expanded into substeps) and jobs which ran at particular times, in chronological order.

You receive information on:

The job status
The job runtime
The update status

Use the right mouse button to see the different functions available for this job, such as:

Start transaction
Restart report
Goto object monitor in the generalized worklist, and so on.

For more detailed information on a job, double-click on the required entry in the structure tree. The detail view appears.

Detail view of a job

By switching the tab titles you can select different detailed information (details, parameters, additional information) on a job.

There are four pushbuttons underneath the tab page. These are only active if corresponding data for the selected job is available:

Spool list
Display of batch spool list(s)
Job log
Display of the job log belonging to the batch job
Extract
Online display of results lists that were saved
Basic list
Online display of a short list that was saved. This list contains the most important information on a job.

Message list

If messages occurred for a job and these were saved, then the system displays them in the message area.

To go to a message long text, double-click on the corresponding message.

Activities

From a scheduled job, you call up the monitor from the daily overview of the scheduler.

You call up the required details for a selected job.

See also:

Monitor - Working with the Object List

sirish.sites@gmail.com (Sirish WebWorld) — Fri, 13 Feb 2009 09:34:00 +0530

Definition

The monitor of the Schedule Manager is a tool for processing multilevel worklists. It contains information on active or completed jobs that were planned in the scheduler.

Use

This section provides information on using the object list in the monitor of the Schedule Manager.

For more information on jobs in the monitor, see Using the Monitor.

The monitor performs the following functions:

Displays the available worklists and their processing steps

Keeps track of the processing status of each object (such as product cost collectors, WBS elements, internal orders, and production orders) and each processing step

Assists you in analyzing the causes of errors for the objects and processing steps

Displays the processing status of objects (particularly for the objects with errors)

Shows the hierarchical relationships between the objects

Compares object hierarchies with each other

Controls whether objects enter the next processing step

Sends objects to the responsible person for further processing

Structure

The monitor is divided into the following screen areas:

Structure Tree with Worklists/Processing Steps/Jobs

The structure tree containing the worklists, processing steps and jobs is displayed on the left side of the monitor.

The system displays the following information on each worklist:

Number of objects in the worklist

Processing steps

Number of objects processed in each processing step

Number of objects with errors in each processing step

Object List

The object list includes the following information:

The objects for the selected processing steps. You can control which objects are displayed for each processing step by means of a filter that takes the individual processing statuses into account. In application toolbar icons for object list, choose the icon Objects: Set status filter
The system uses the last user-specific default setting of the dialog box. Note the default settings of this dialog window in the SAP standard system. The last user-specific setting of the dialog box is the default.
The processing step performed for the object
The processing status of the object for each processing step
A check box you can select to indicate that you have processed the object in the worklist monitor
The person responsible for the object (if any)

Message List

See also:

Schedule Manager: Multilevel Worklist

Multilevel Worklist: Process Flow

For detailed information on using the monitor of the Schedule Manager, see the following section:

Processing Status of Objects and Processing Steps

Processing Worklists

Error Handling

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 16:16:00 +0530

Job error handling involves the following:

For checking purposes:

Periodically reading the job status
Checking the maximum runtime

When errors occur:

User decision "Continue the flow with the next task"
User decision "Reschedule the job"

The user decision "Reschedule job" is not available for worklists.

Error: A Job Stops

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 16:14:00 +0530

Cause

The job stops, if for example, the system is turned off.

Error Handling

The dialog for an error in the job administration is handled in its own sub-workflow, which consists of a user decision. This message is sent as a top priority mail to the person whose name is entered in the detail screen for maintenance of jobs in the flow definition, in the When error, mail to section (see also: Creating a Flow Definition). That person receives the mail that an error has occurred in job XY in their mail inbox.

There are two options in the user decision.

Continue the flow with the next task

You choose this option if:

You corrected the error and rescheduled the job manually in a separate session, and are waiting for the job to be executed.
You executed the transaction online.
You decided that the error is not relevant.

You can use this option without any problems, for jobs that have worklists. However, you need the worklist ID to be able to execute the job outside of the workflow.

Reschedule the job

You choose this option if you corrected the error and would like to use the Schedule Manager to control the rescheduling of the job.

Graphical Representation of the Flow

Error: A Job Becomes "Stuck"

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 16:13:00 +0530

Symptom

The program has a runtime that is far longer than expected.

Error Handling

The dialog for a processing error in the program is handled in its own sub-workflow. which consists of a user decision. This message is sent as a top priority mail to the person whose name is entered in the detail screen for maintenance of jobs in the flow definition, in the When error, mail to section (see also: Creating a Flow Definition). That person receives the mail that an error has occurred in program X, variant Y in their mail inbox.

There are two options in the user decision.

Continue the flow with the next task

You choose this option if:

You corrected the error and rescheduled the job manually in a separate session, and are waiting for the job to be executed.
You executed the transaction online.
You decided that the error is not relevant.

You can use this option for jobs that have worklists. However, you need the worklist ID to be able to execute the job outside of the workflow.

Reschedule the job

You choose this option if you corrected the error and would like to use the Schedule Manager to control the rescheduling of the job.

Graphical Representation of the Flow

Error: An Executed Report Found an Error

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 16:11:00 +0530

Symptom

Due to an error in the content, the REPORTERROR workflow event was triggered.

Error Handling

The workflow executes an error dialog. This contains a user decision. The user decision is sent as a top priority mail to the person whose name is entered in the detail screen for maintenance of jobs in the flow definition, in the When error, send to section (See also: Creating a Flow Definition). That person receives the mail that an error has occurred in program X, variant Y in their mail inbox.

There are two options in the user decision.

Continue the flow with the next task

You choose this option if:

You corrected the error and rescheduled the job manually in a separate session, and are waiting for the job to be executed.
You executed the transaction online.
You decided that the error is not relevant.

Reschedule the job

You choose this option if you corrected the error and would like to use the Schedule Manager to control the rescheduling of the job.

No user decision is called up for jobs that have worklists. This is because the error handling for worklists is triggered by rerunning the task steps in the workflow. Therefore, programs written for worklists always trigger the FINISHED event.

Graphical Representation of the Flow

Error: Job Scheduling Was Unsuccessful

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 16:10:00 +0530

Cause

Scheduling a job can be unsuccessful if the technical name of the report or variant was changed after the flow definition was created. This means that the technical names in the flow definition no longer exist.

Error Handling

The workflow recognizes the error and issues an error message displaying the faulty technical name of the report or variant.

The message is linked to a user decision. This message is sent as a top priority mail to the person whose name is entered in the detail screen for maintenance of jobs in the flow definition, in the When error, mail to section (see also: Creating a Flow Definition). That person receives the message in their mail inbox.

There are two options in the user decision.

Continue the flow with the next task

You choose this option if:

You corrected the error and rescheduled the job manually in a separate session, and are waiting for the job to be executed.
You executed the transaction online.
You decided that the error is not relevant.

Reschedule the job

You choose this option if you corrected the error and would like to use the Schedule Manager to control the rescheduling of the job.

Error: The Workflow Stops

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 16:10:00 +0530

Cause

The workflow stops due to an error in the workflow runtime system.

Symptom

The job just scheduled is completed since the job control functions separately from the workflow. However, the following steps in the flow definition are no longer executed.

Error Handling

It is not possible to restart at the point where the workflow stopped. Therefore, you need to reschedule the whole flow definition.

Error: The Workflow Becomes "Stuck"

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 16:07:00 +0530

Cause

During job scheduling using the workflow, if an error occurs in the program section of the report and the report is being run at the AT SELECTION-SCREEN OUTPUT event, then the job is not scheduled.

Error Handling

The system issues an error message to notify you that scheduling is not complete.

There are two options in the user decision.

Continue the flow with the next task

You choose this option if:

You corrected the error and rescheduled the job manually in a separate session, and are waiting for the job to be executed.
You executed the transaction online.
You decided that the error is not relevant.

Reschedule the job

You choose this option if you corrected the error and would like to use the Schedule Manager to control the rescheduling of the job.

Using the Flow Definition

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 16:06:00 +0530

Use

A flow definition consists of individual flow steps. These steps include scheduling programs with variants in the job control of the SAP System, and interaction with users by email.

The flow definition ia a graphical summary of several steps. A step in the flow definition corresponds to a task in the task plan, except that the individual step does not appear directly in the task plan, rather it is displayed in the flow definition, which is included in the task plan.

Integration

The Schedule Manager provides a multilevel worklist. The multilevel worklist improves performance and facilitates error finding. To use the Schedule Manager worklist, create a flow definition and schedule it in the scheduler. For further information about this worklist, see Choosing Objects for Processing.

Prerequisites

Workflow profiles enable you to adapt the user interface of the flow definition according to your requirements. If required, the project team can create and provide this type of profile. To make individual processing available as flow steps, you need a program which provides all the processing parameters and displays an ergonomic user interface.

If you are using the workflow builder function for the first time in the SAP System, go into Customizing and choose Basis ® Business Management ® SAP Business Workflow ® Maintain Standard Settings for the SAP Business Workflow and then Automatic Customizing.

For more information, see Creating a Flow Definition.

For more information on error handling in flow definitions, see: Error Handling.

Features

You can define individual flow definitions with as many flow steps as you like, or you can link flow definitions together within an "upper" flow definition. You must assign the "upper" flow definition to an application (or application component) that is on a higher level than the applications assigned to the lower-level flow definitions.

Flow Step Types

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 16:06:00 +0530

In the workflow builder, you can schedule four types of flow step:

Program with Variants

Enter a program and a variant.

User Decision

For a user decision, the system sends a message to a user. The system generates a text that creates a message header in the user’s inbox. The system stops processing the individual tasks in the flow definition until the user confirms the message. The text should therefore contain the information required to make the decision, such as which task the system just executed and which data needs checking.

Fork

You can define as many tasks as you wish in each of the parallel branches. All of the parallel branches join at the end, although the task that follows the join is only processed when all of the tasks in each branch are completed.

You cannot subsequently change the number of parallel branches. However, you can delete a branch by deleting all of the tasks in the branch. You cannot add another branch.

Flow Definition

The flow definition consists of several tasks that the system executes in the specified order, once you schedule the flow definition in the daily overview of the scheduler. You can create further "sub-" flow definitions within a flow definition.

In the workflow builder, you can schedule four types of flow step

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 16:04:00 +0530

Use

You use a flow definition in the Schedule Manager. You can insert a flow definition in the task list of the scheduler, then schedule it into the daily overview and run it.

Procedure

Choose Extras ® Process flow definition in the Scheduler

Enter a description for the flow definition

Choose Create.

When creating without a template, the system generates a flow definition example (with flow steps) for the specified application. Do not delete the steps Check objects in worklist and Renew worklist processing, because these steps enable the recursive call of worklist processing. If the step Renew worklist processing is deleted, you cannot include it in the flow definition.

In the screen that follows, enter a description for your flow definition and then assign it to an application component.

Note that all flow steps in a flow definition (which is also assigned to an application) must also be assigned to this application or to the application on the next level up or down.

If required, indicate that you are working with a

worklist

. To work with a multi-level worklist, you must have chosen an application with a worklist and the function With worklist during creation.

Enter a development class in the dialog box Create object catalog entry, then save your entry.
The workflow builder appears. Each node (step, event or operator) in the workflow builder has a menu that you can call up using the right mouse button. This immediately shows you the operations that are possible for a node, and cancels out the need for long menu structure or pushbutton paths.

In the navigation area, select the node Steps.

Choose Create step.

Choose the

flow step type

Specify the required information for the flow step.

You can choose programs only using the input help. Programs are displayed in the input help only if you have registered them in the tables SCMAPROGRAMS (for SAP programs) or SCMAPROG_CUST (for your own programs).
For more information about working with your own programs, see Inserting Own Programs as Tasks.

Choose Cancel to return to the Workflow Builder.

You see the task in the structure tree of the task area. The task is integrated in the graphic of the flow definition. Move the task to the desired position in the flow definition.

Save your entries.

For more information on the Workflow Builder, see the SAP Library under BC-Basis Components ® Business Management (BC-BMT ) ® SAP Business Workflow Navigation(BC-BMT-WFM) ® Workflow Builder.

If you are using the workflow builder function for the first time in the SAP System, go to the Implementation Guide (IMG) and choose Basis ® Business Management ® SAP Business Workflow ® Maintain Standard Settings for the SAP Business Workflow and then Automatic Customizing.
You can also use the SAP standard flow definitions. Variant names for these flow definitions begin with SAP& These variants only contain selection variables named SAP-SCMA Use the STVARV transaction or Schedule Manager, Extras ® Settings ® Selection variables to adapt the variable values according to your requirements. For further information on selection variables, see Defining Global Variables for Task Lists/Flow Definitions and Defining Selection Variables for Flow Definitions With Parallel Branches.

Specifying Selection Variables for Flow Definitions With Parallel Branches

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 16:03:00 +0530

Use

Normally the selection criteria for period-end closing do not change very often. Criteria that do change regularly are the closing period and the fiscal year. The period and fiscal year must be changed for each program or flow definition specified as a task in the task list.

To avoid having to change these values for every single program or every flow definition, you can define selection variables in the program variants.

You have five programs that must run with the same valuation for nine plants. That means that every program must run with a plant-specific variant for each plant. These variants differ only in their Plant specification.

As described below, you define global variables for fiscal year, period and plant . Create variants for the five programs and define the global variants that you created previously. Finally define a flow definition (A) for the five programs. Define a flow definition (B) with nine parallel branches (for the plants). Include the flow definition A in each of these branches. A dialog box appears that displays the three global variables (fiscal year, period, plant). Enter a value for the variable Plant and flag the entry as to be saved. The dialog box reappears when you plan flow definition B in the day view. Enter values for each fiscal year and period. Do not make an entry for the variable Plant. If you make an entry here, the system does not accept it. You defined the plant when creating the flow definition.

Prerequisites

Y ou have defined the variables already. For more information, see Defining Selection Variables.

You are in flow definition in Schedule Manager (Extras ® Flow definition ® Edit flow definition).

Choose a processing step in the navigation area.
On the right of the screen, you see Flow definition: Task details.

Enter a new variant for this processing step and define a name for this new variant in the Variant field .

Choose Change variant.
The Maintain Variant: Program , Variant screen appears.

Procedure

Choose Attributes.

Make an entry in the Description field.

Now you want to specify variables for the period and fiscal year that you can then change once centrally for all programs and flow definitions that use those variables. To do this, under the heading Selection screen objects, select the column S in the lines Period and Fiscal year.

Choose Selection variables.

To choose selection criteria for the variables P_FROM (period) and P_GJAHR (fiscal year), use the input help.

You previously entered these variables in table TVARV.

Save your entries.
The Maintain Variant: Program , Variant screen appears.

Result

The system uses these entries for the following purposes:

To feed these variables to a program created directly as a task in the workflow.

To feed these variables to the parallel branches.

The system mixes the variables of the parallel branches with those of the main workflow.

If the parameter values of the main workflow are different from those of the subworkflows, the system uses the parameter values that were specified when the subworkflows were created.

Choosing Objects for Processing

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 16:02:00 +0530

Use

An advantage of this worklist is that the objects for processing only have to be selected once per flow definition.

Prerequisites

You are in flow definition in Schedule Manager (Extras ® Flow definition ® Edit flow definition).

Procedure

Choose a processing step in the navigation area.
On the right of the screen, you see Flow definition: Task details.

Enter a new variant for this processing step and define a name for this new variant in the Variant field .

Choose Create variant.
The Variant Maintenance screen appears. Program , variant .
Here you can determine the scope of selection of the program variants for the flow definition.

To be able to choose more extensive selection criteria, first complete the required entry fields, for example Period <

006

>, Fiscal year <

2000

You can now define further selection parameters using the various pushbuttons that are offered in dialog boxes.

Choose Attributes.
The ABAP: Save Attributes of Variant screen appears.

Defining Processing Options, Output Options and Execution Types

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 16:01:00 +0530

You are in flow definition in Schedule Manager (Extras ® Flow definition ® Edit flow definition).

Choose a processing step in the navigation area.
On the right of the screen, you see Flow definition: Task details.

Choose Change variant.
The screen Variant Maintenance appears. Program , variant .

In the corresponding group frames, select the desired processing option, output option and execution type. For example, you can define whether parallel processing is allowed.

Perform variant maintenance for all programs that are linked to the flow definition.

For further information see Defining Selection Variables in the Program Variants and Selection Variables for Flow Definitions with Parallel Branches.

Controlling - CO

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 16:00:00 +0530

Controlling (CO)

free download CO External Data Transfer

sirish.sites@gmail.com (Sirish WebWorld) — Tue, 10 Feb 2009 15:59:00 +0530

CO External Data Transfer