The report is designed in PF1 & WP1 to extract CO cycle master data with standard ALV layout, which is compatible for kinds of cycles, including:

    • COPA Actual assessment cycle

    • COPA Plan assessment cycle (not used in RCS)

    • Cost center Actual Assessment cycle

    • Cost center Plan Assessment cycle

    • Cost center Actual Distribution cycle

    • Cost center Plan Distribution cycle

 

 

Column label in report output

As a cycle consists of kinds of information at header / segment level, and in each segment, there are fields for sender / receiver respectively, and even for receiver side, the percentage split can be applied for multi-receiver objects.

So, to facilitate identifying the column nature and improve the report understandability, a prefix is assigned for each column label:

  • ‘[H]’ stands for header level data, for example ‘[H]Cycle’.
  • ‘[S]’ stands for segment general data, for example ‘[S]Segment Name’.
  • ‘[S-S]’ stands for segment sender data, for example ‘[S-S]Sender Cost Center / grp’
  • ‘[S-R]’ stands for segment receiver data, for example ‘[S-R]IECRA’
  • ‘[S-T]’ stands for segment receiver (or sender) multi objects split data, for example ‘[S-T] Factor Value’.

Two options available in output

As a cycle allows for the percentage split in the case of multi receiver objects, it makes difficult to show all information in a single output with good understandability.

With this consideration, 2 output options are designed:


  • Standard output

    • Each row represents a unique segment in a cycle, showing cycle header data / segment general data / sender data / receiver data.

    • But multi-object split info is excluded here.

    • Column with ‘[S-T]’ prefix in label is not available in the option.

  • Extended output with multi-object split

    • This layout is recommended ONLY when user needs to check the multi-object split percentage.

    • Column with ‘[S-T]’ prefix in label is feed in the option.

    • All multi-object split info is showed as extra rows, means, all rows showed in Standard layout will be showed here as well exactly, but append some extra rows which are dedicated to show the multi-object split info. In other words, Extended output = Standard output + extra entries for multi-object split info.

 

Coloring the entries for multi-object split info

  • In Extended output with multi-object split, the extra entries for split info is highlighted in light green color. See below picture for example.
  • PS: Another way to differentiate the extra entries is to use one of below 2 columns:
  • [S-T] Sender / Receiver Indicator. When it is not Null, it’s the extra entries.
  • [S-T] Item Number. When it is not Null, it’s the extra entries.

 

 

Tips to know the cycle category

 Below 3 columns can be used to understand the feature of certain cycle.

  • [H]Table, to know it’s cost center or COPA cycle 
    • CCSS -- Cost center cycle
    • CE7Z0xx -- COPA cycle (Z0xx is the operation concern code)
  • [H]Actual/plan indicator, to know it’s Actual or Plan cycle.
    • I --  Actual
    • P --  Plan
  • [H]Type of allocation, to know it’s Assessment or Distribution cycle.
    • U -- Assessment
    • V -- Distribution
    • L -- Indirect activity allocation
    • … etc.

 

Receiver / Sender multi-objects split

  • In WP1, the percentage split is widely used at receiver side for multi-object case. But in some limited case, a specific amount is given to individual cost elements to restrict the allocation at sender side. For the both cases, in the report output, the information will be showed in the same columns with prefix ‘[S-T]’.  

  • For users, to know the split information is for receiver or sender, column ‘[S-F]Sender / Receiver Indicator’ can answer,

    • when the value is ‘R’, the entry is for receiver factor,

    • when the value is ‘S’, the entry is for sender factor. 

 

 

Combine ‘from’ ‘to’ ‘group’ into one field

  • When creating a cycle, to specify sender / receiver, user can input ‘from’ only to show a single object, or input ‘from’ and ‘to’ to show a range, or even use ‘group’ to show a collection list.
  • In order to reduce the column quantity in the report output, the information in ’from’ ‘to’ ‘group’ is combined into one single column.   

‘[H]Cycle’ code start with operation concern

  • When put cycle code as selection criteria, please start with the operation concern code then follow by cycle code, as this is the way SAP store the cycle master data in tables.   
  • As a tip, all below options work