Executing Periodic Repostings or Periodic Allocations Online

Prerequisites

Creating Cycles

Before you can execute a periodic reposting or a periodic allocation for one or more cycles, you must already have created the corresponding cycle(s) (see: Defining Periodic Repostings or Periodic Allocations).

Periodic Reposting or Allocation: Access

	Periodic Repostings	Periodic Allocations
Plan	Accounting Controlling Cost Center Accounting Planning Planning aids Periodic Reposting	Accounting Controlling Cost Center Accounting Planning Allocations Relevant allocation or Accounting Controlling Activity-Based Costing Planning Allocations Relevant allocation
Actual	Accounting Controlling Cost Center Accounting Period-end closing Single functions Periodic Reposting or Accounting Controlling Activity-Based Costing Period-end closing Single functions Periodic Reposting	Accounting Controlling Cost Center Accounting Period-end closing Single functions Relevant allocation or Accounting Controlling Activity-Based Costing Period-end closing Single functions Relevant allocation

Note Note

If you have large amounts of data to process, SAP recommends executing periodic repostings or periodic allocations in the background. This enables you to run these postings at times when system usage is at its lowest (see Executing Periodic Repostings or Periodic Allocations in the Background).

End of the note.

Procedure

Enter the period or the period interval, and the fiscal year, for which you want to execute the periodic reposting or periodic allocation.
If you first want to execute periodic reposting or periodic allocation without carrying out an update and checking the results in the lists, you should adopt the default settings for Test run.
If you select Test run, the system executes the periodic reposting or the periodic allocation, but does not update the database.

If you want to execute periodic reposting or periodic allocation with update, deselect Test run.
The standard settings if for the system to display the Basic list for the cycle processing, which list displays all executed cycles. If errors occurred during processing, you can analyze these using the basic list. You can also use the Segment list to display the segments for each cycle (see: Displaying Segment Lists).
From the basic list and the segment list, you can branch to the line item display (containing the plan and actual line items created on the sender and receiver side) (see: Results of Periodic Repostings or Periodic Allocations).

To display other lists, choose List selection. You can display (and print) sender and receiver lists (see Displaying Sender Lists) or journal lists (see Displaying Journals).
Enter the cycle(s) for which the periodic reposting or periodic allocation is to be executed.
Under Settings, make the following entries:
1. To vary the display of the different lists (basic list, sender list, receiver list, segment list, and journal list) use input help to select one of the three default display variants.
  
  The expanded period display 1RKS_DEF is set as the standard.
  
  You can change this setting on the list screen:
  1. To do so, choose Settings Display variant Select and select one of the existing display variants.
  2. Choose Current display variant and adjust the list display accordingly. Now choose Copy and save the list display under a new name. To do so, choose Settings Display variant Save .
    You can then use a display variant with this name for all lists (basic list, sender list, receiver list, segment list and journal list). In this way, you can save all five lists according to your individual needs.
    
    Note
    Note that if you select the summarized period display 1RKS_DEF_PER as a display variant, the system evaluates totals records only.
    
    You can create the display variants for specific components.
    
    End of the note.
2. To determine the way in which the database is accessed, enter the database in the dialog box.
  Database selection in the standard is by cycle. If this setting would lead to too many objects being selected (leading to poor system performance) you should select a different setting.
3. To store an extract when executing a cycle, select Store extract under in the dialog box and enter an extract.
  This facility enables you to display a results list that generated a batch job.
  
  To display the data belonging to the extract choose Goto Extract Management . The same navigation functions are available as those when carrying out the cycle online. For example, you can display the senders of a segment separately.
4. If the processing of a cycle has already been terminated with an error message or it has supplied incorrect results, you can generate and print a flow trace log when executing the cycle. This logs all data relevant to the error search.
  To do so, select Flow trace on in the dialog box.
  
  If you activated the flow trace log, you can display it after processing by choosing Technical statistics (see: Technical Statistics, Expert Trace, and Divergence Analysis).
5. To check processing of cycles, you can (per allocation type) log the runtimes of the sub-areas of a cycle execution. To do so, select Runtime analysis on in the dialog box.
  To display the logs, choose Goto Runtime analysis .
6. If you want to execute several cycles in a collective start, you can specify whether the system should end the periodic reposting or periodic allocation, or whether it should continue executing the follow-on cycles.
  1. If the cycles in the collective start are linked and follow-on errors can be expected, choose End program.
  2. If the cycles in the collective start are not linked, and you want to output all errors in one run, choose Change to simulation mode.
7. To execute several cycles of the same allocation type in parallel, you must first assign these cycles to different cycle run groups (see: Processing Cycle Run Groups).
  To execute a consistency check, choose Test obligatory. The test run checks whether you are allowed to execute the selected cycles in parallel.
  
  Note
  Choose Extras Cycle run groups to access the Cycle run group: Overview screen. To start the check report, choose Check cycle run groups.
  
  In this report, the system controls whether cycles that are using the same organizational units (company code, business area, and so on) are assigned to different cycle run groups. The system checks, for example, whether the objects of a company code exist in different cycle run groups. If this were the case, it could lead to inconsistencies when you execute the cycles in parallel.
  
  End of the note.
To enable you to easily repeat the periodic reposting or periodic allocation at a future date with the same entries, the system lets you save your entries as variants.
1. Choose Extras Variant Save and enter a name and, if necessary, a short text for the variant.
2. To transfer variants to the initial screen, choose Extras Variant Get . Use the input help (F4), to display a list of saved variants, from which you can select the variant you require.
3. To delete a variant, choose Goto Variant Delete . You can specify whether you want to delete the variant(s) in all clients or only in the current client.
  
  Note
  You can only call up and use variants within the same component, the same allocation type (e.g. assessment), as well as divided according to actual and plan.
  
  End of the note.
To display the basic list, choose Execute (see: Results of Periodic Repostings or Periodic Allocations).
To post (with update) the periodic reposting or periodic allocation:
1. Return to the initial screen.
2. Deactivate Test run.
3. Choose Execute.

More Information

Displaying the Cycle Overview