Skip to Content
0
Former Member
Dec 14, 2015 at 12:24 PM

settlement rule cat. WBS - receiver=sender

510 Views

Hi,

I have the following scenario:

  • POC project, with billing flag on level 1. RA key on this level. Several 2,3,4,5 levels below.

  • As per a new requirement, hours booked on certain 5th levels(example, let’s call it level X), must be settled to other elements inside the same structure (let’s call it level Y). POC SETTLEMENT MUST NOT BE AFFECTED BY THIS NEW ENHANCEMENT. ONLY HOURS VALUES (CAT2 postings) HAVE TO BE SETTLED ON THE OTHER WBS LEVELS

In order to fulfil the enhancement, I created a source structure with 2 source assignments, let’s call them AAA (cost elements from 900000 to 999999) and BBB (cost elements from 400000 to 499999).

Here’s how I fulfilled the requirement:

  1. Source assignment AAA is linked to CAT2 postings on level Y (CAT wbs). Assignment BBB is linked to the remaining who doesn’t have to be settled on level Y.

WBS ELEMENT: X

Distribution rule:

Cat

settlement receiver

%

sett. type

source assignment

WBS

Y

100

FUL

AAA

2.Cost elements linked to assignment BBB settle on the sender (error message kd 118 removed through message handling)

WBS ELEMENT: X

Distribution rule:

Cat

settlement receiver

%

sett. type

source assignment

WBS

Y

100

FUL

AAA

The solution seems to work, but the disadvantages are the superfluous line items generated by the system when performing the settlement in point 2.

Does any one of you could suggest a cleaner and better solution? Will it be possible, someway, by means of a standard solution, to avoid the settlement of elements with source assignment AAA?

Thanks in Advance for your help!