Create Distribution Cycle

Create Create Distribut Dist ribution ion Cycle Cycle

MEETING DATE:

SAP TRANSACTION ENTRY: KSV1 – Create Distribution Cycle KSV2 – Change Distribution Cycle INQUIRY: KSV3 – Display Distribution Cycle

BUSINESS OWNER: Janice Tanner SYSTEMS SYSTEMS OWNER: Janis Pritchard Beth Beshears

AUTHOR:

WHEN/PROMPT: HOW OFTEN:

As needed.

Monthly

BRIEF INPUT: BRI EF OUTPUT (IF APPLI CABLE): DETAILED DESCRIPTION OF PROCESS: I . Create Distribution Cycle The Distribution cycle is created as part of configuration in the development client and ported to production. Key transaction code KSV1 Key cycle name and start date on the initial screen Attach a segment Define the segment variables by completing each of the tabs Save the cycle • • • • •

Note: Sender/Receiver options that will be used by Oxford Sender Rule Value Origin Receiver Rule Posted Amounts Actual or Plan Value Fixed Percentages Posted Amounts Actual or Plan Value Variable Portions Posted Amounts Actual or Plan Value Variable Portions Posted Amounts Actual or Plan Value Variable Portions

Variable Portion Type N/A Actual Costs Planned Costs Actual Stat Key Figures

I I . Change Distribution Cycle All cycle information may be changed using transaction code KSV2 If a cycle definition is already in use, it is suggested that instead of changing the c ycle, you create a new one to use for that date forward • •

I I I . View . View Distribution Cycle Key transaction code KSV3 •

\\oxsol\Documents\GL\BPP\RecurringEntry.doc

1

8/18/2009

Create Create Distribut Dist ribution ion Cycle Cycle

I. Create Distribution Cycle

KSV1 – Create Actual Distribution Cycle: Initial Screen FI ELD N A M E Cycle Start Date

R / P / C/ C/ N R

U S E R A C TI O N / DE D E S C R I P TI O N Key cycle name

R

Key the cycle start date

C O M M EN EN TS Max length is 6 characters The starting date for the cycle has the following two purposes: 1. It determines the earliest validity date of the cycle. 2. By assigning different starting dates you can define different variants for one cycle.

Copy From Cycle

C

If you wish to copy an existing cycle, key the cycle name

Start Date

C

Will pre-fill from selected cycle

Controlling Area

C

Will pre-fill from selected cycle Click Enter Click Enter


2

8/18/2009

Create Distribution Cycle

Create Actual Distribution Cycle: Header Data FI ELD N AM E Controlling area

R / P/ C / N P

USER ACTI ON / DESCR IP TI ON Pre-fills

Cycle

P

Pre-fills from previous screen

Status

P

Start Date

P

Pre-fills from previous screen

To Date

R

Key the cycle end date Pre-fills with the fiscal year end date

Text

R

Key a description of the cycle

Iterative

N

NOT USED

Cumulative

C

Select if you wish to ‘catch up’ an allocation.


COM MEN TS

Will display as ‘New’ for an unsaved Distribution cycle

3

The end date defines the end of validity for the cycle. You cannot process any periods which are not within the validity period for this cycle.

If this indicator is selected, the cycle is repeated until each sender is fully credited (a small remainder may be left over in some cases). If you execute a cycle with the cumulative indicator set to active, then the sender amounts posted up to the current period are allocated based on tracing factors, which are cumulated from period 1 onwards. In the 8/18/2009

Create Distribution Cycle current period, the allocation amounts determined are posted less the amounts allocated in the previous periods.

Derive Func Area

N

NOT USED

Derive Functional Area from Recipient Oxford will not use Functional Areas

Consumption

NOT Used

Object Currency

P

Transaction Currency

C

Defaults to checked

The sender values in the object currency are computed separately and distributed in separate fields. This only functions when the object currency of all the affected objects (cost centers, orders...) is the same, since no translation between object currencies takes place during processing.

The posted sender values in the transaction currency are computed separately, processed internally and updated to the receiver in the posted transaction currency.

Select


If you select this option, the posted consumption quantities are also distributed. A pre-condition is that quantities must be entered on all the senders. If a quantity is missing on a sender, the SAP System issues a warning and the quantity cannot be distributed.

to define a cycle segment

4

8/18/2009

Create Distribution Cycle Segment with Sender: Posted amounts; Receiver: Fixed Percentages

R/ P / C/ N R

Segment Header Screen USER ACTI ON/ DESCRI PTI ON Key a name for the Distribution segment

Description

R

Key a description of the segment

Lock Indicator

C

Sender rule

R

FIELD NAM E Segment Name

COM M ENTS Max length 10 characters Note: This is NOT the operating group segment

The segment will not execute while this is set ‘On’ Select Posted Amounts as the sender rule.

This field controls how the sender values are calculated The posted amounts on the sender serve as the sender values.


5

8/18/2009

Create Distribution Cycle Share in %

R

Enter the percentage of the posted amount that will need to be allocated. In most cases, it should be 100% of the posted amounts

By entering a percentage less than 100%, you can stipulate that only a portion of the sender value is distributed. The remaining amount is left on the sender. You are not permitted to enter a percentage greater than 100%. If a sender occurs in more than one group, the system checks that the total of the percentage amounts does not exceed 100%.

Select if sender values are based on actual values R

Act Vals

Indicator ensuring reference to actual values as sender values when processing the allocation with the sender rules "posted amounts" and "posted quantities”

OR

Plan Vals

R

Select if sender values are based on plan values

Receiver rule

R

Select Fixed Percentages as the receiver rule


6

Indicator ensuring reference to plan values as sender values when processing the allocation with the sender rules "posted amounts" and "posted quantities". Fixed percentages: You define fixed percentages for the receivers in the Tracing Factor screen. The value from the sender is distributed to the receivers according to this percentage. The total of receiver tracing factors must not exceed 100%. The sender base must be fully distributed. If the total of the receiver tracing factors is less than 100%, then a portion of the sender value remains on the sender.

8/18/2009


Senders/Receivers Tab FI ELD N AM E Sender

R / P / C/ N

Cost Center

R

Functional Area

N

Cost Element

R

US ER ACTI ON / DES CR IP TI ON

COM M EN TS

Enter the cost center, cost center range or cost center group that is the sender of the allocation NOT USED

See creation of Cost Center group BPP

Enter the sender cost element (nominal) , the cost element range or cost element group

These are the nominals that are holding the posted amounts For more info on Cost Element groups, see the Cost Element Group BPP

Receiver Order

N

NOT USED

Cost Center

R

Functional Area

N

Key the receiving cost center, cost center range or cost center group NOT USED


7

8/18/2009

Create Distribution Cycle Cost Object

N

NOT USED

Sender Values Tab FI ELD N AM E Share in % Actual Value Origin/Plan Value Origin Version

R / P/ C / N P

USER ACTI ON / DESCR IP TI ON Pre-fills from Segment Header Tab

P

Pre-fills from Segment Header Tab

C


COM MEN TS

Key or select the version of the budget to If you selected Actual Value origin, always be used for Planned Values key or select 0 as the version In most cases, this will be version 0

8

8/18/2009


Receiver Tracing Factor Tab FI ELD N AM E Cost Ctr

R / P / C/ N P

Portion/Percent

US ER ACTI ON / DES CR IP TI ON Pre-fills from Senders/Receivers Tab Key the percent to be allocated to each cost center

COM M EN TS

If the fixed percentages tracing factor is selected on the Segment Header tab, this field is used to define fixed percentages for the receivers in the Tracing Factor screen. The value from the sender is distributed to the receivers according to this percentage. The total of receiver tracing factors must not exceed 100%. The sender base must be fully distributed. If the total of the receiver tracing factors is less than 100%, then a portion of the sender value remains on the sender.

If you wish to validate the cycle, click on the Segment Header tab and select Cycle > Check > Formal Check Click \\oxsol\Documents\GL\BPP\RecurringEntry.doc

to save the cycle. Click 9

to create a new segment 8/18/2009

Create Distribution Cycle Segment with Sender: Posted amounts; Receiver: Variable Portions; Portion Type: Actual Costs

R/ P / C/ N R


Description

R


Lock Indicator

C

Sender rule

R






10

8/18/2009


R

Enter the percenetage of the posted amount that will need to be allocated. In most cases, it should be 100% of the posted amounts

By entering a percentage less than 100%, you can stipulate that only a portion of the sender value is distributed/assessed. The remaining amount is left on the sender. You are not permitted to enter a percentage greater than 100%. If a sender occurs in more than one group, the system checks that the total of the percentage amounts does not exceed 100%.

Select if sender values are based on actual values R

Act Vals

Indicator ensuring reference to actual values as sender values when processing the allocation with the sender rules "posted amounts" and "posted quantities

OR

Plan Vals

R


Receiver rule

R

Select Variable Portions as the receiver rule

Var Portion Type

Scale Neg Tracing Factors

R P

Indicator ensuring reference to plan values as sender values when processing the allocation with the sender rules "posted amounts" and "posted quantities". Variable portions: The tracing factors are determined automatically from the totals record file. You define the criteria for this database access in the Tracing Factor screen.

Select Actual Cost from the drop down list Pre-fills with selection ‘No Scaling’ Leave as default

Key the Senders/ Receivers tab and the Sender Values tab as described above


11

8/18/2009


Receiver Tracing Factor Tab FI ELD N AM E Var portion type

R / P/ C / N P

Scale Neg Tracing Factors Cost Element

P

Pre-fills from Senders/Receivers Tab

R

Key the cost element, cost element range or cost element group the posted amounts of which will determine the percentage allocated to each receiver cost center specified on the senders/receivers tab


USER ACTI ON / DESCR IP TI ON Pre-fills from Senders/Receivers Tab

12

COM MEN TS

The calculation may further be affected by the Receiver Weights keyed on the next tab

8/18/2009


FI ELD N AM E Factor Per Weighting Factor

R / P/ C / N P

USER ACTI ON / DESCR IP TI ON Pre-fills with 100

COM MEN TS

R

Key 100 by each cost center

Do not key a factor other than 100. A factor of 100 ensures that the portion calculated from the posted amounts will be used to determine the allocation

If you wish to validate the cycle, go to the Segment Header tab and select Cycle > Check > Formal Check Click


to save the cycle. Click

13

to create a new segment

8/18/2009

Create Distribution Cycle Segment with Sender: Posted amounts; Receiver: Variable Portions; Portion Type: Planned Costs

R/ P / C/ N R


Description

R


Lock Indicator

C

Distribution CELe

R


Allocation Structure


The segment will not execute while this is set ‘On’ Enter the nominal for the Distribution account

C


The Distribution account is a secondary cost element which feeds into a primary nominal account that is tied to the Profit Center Hierarchy

Key instead of an Distribution cost element to specify which cost elements should be allocated under which Distribution cost elements within an allocation structure 14

8/18/2009

Create Distribution Cycle Sender rule

R

Select Posted Amounts as the sender rule.


Share in %

R

Enter the percenetage of the posted amount that will need to be allocated. In most cases, it should be 100% of the posted amounts


Actual Value Origin

R

Select if sender values are based on actual values


OR

Plan Value Origin

R


Receiver rule

R


Var Portion Type


R P


Select Planned Cost from the drop down list Pre-fills with selection ‘No Scaling’ Leave as default



15

8/18/2009



R / P/ C / N P

Scale Neg Tracing Factors Version

P

Cost Element


COM MEN TS

Pre-fills from Senders/Receivers Tab R

R

Key or select the version of the planned values upon which the allocation will be based Key the cost element, cost element range or The calculation may further be affected by the Receiver Weights keyed on the next tab cost element group the posted amounts of which will determine the percentage allocated to each receiver cost center specified on the senders/receivers tab

Key the Receiving Weighting Factors tab as described above If you wish to validate the cycle, select Cycle > Check > Formal Check Click


to save the cycle. Click 16

to create a new segment 8/18/2009


Segment with Sender: Posted amounts; Receiver: Variable Portions; Portion Type: Actual Stat Key Figures

R/ P / C/ N R


Description

R


Lock Indicator

C

Sender rule

R






17

8/18/2009


R

Enter the percentage of the posted amount that will need to be allocated. In most cases, it should be 100% of the posted amounts


R Select if sender values are based on actual values

Actual Vals


OR

Plan Vals

R


Receiver rule

R


Var Portion Type


R P


Select Actual Statistical Key Figures Pre-fills with selection ‘No Scaling’ Leave as default



18

8/18/2009



R / P/ C / N P

Scale Neg Tracing Factors Stat Key Fig

P

Pre-fills from Senders/Receivers Tab

R

Select the statistical key figure the posted amounts of which will determine the percentage allocated to each receiver cost center specified on the senders/receivers tab N Not Used

Activity Type


COM MEN TS

Key the Receiving Weighting Factors tab as described above If you wish to validate the cycle, go to the Segment Header tab and select Cycle > Check > Formal Check Click


to save the cycle. Click

19

to create a new segment

8/18/2009

Create Distribution Cycle SECURITY M ATRIX TRANSACTION CODE KSV1

COR FIN REPORTING

I NQ/ R P T

I NQ/ R P T/ I N TR AY

A CCOUN TI NG

KSV2 KSV3

x

x

x

x

ACCTG M GR FUNCTIONS x

ADMIN FUNCTIONS x

x

x

x

x

ISSUES:

BPP CORRECTIONS (IF APPLICABLE):

This section to be completed by the BPP author SUBMITTED FOR APPROVAL (DATE)


RETURNED FOR CORRECTIONS (DATE)

20

RETURNED FOR APPROVAL (DATE)

8/18/2009

Create Distribution Cycle

Recommend Documents