Skip to Content
avatar image
Former Member

Sales Order Settlement to CO-PA with RA

Hi Gurus,

Here is the thing:

  • We have a Line ID of category E (Revenues, included in WIP and RA)
  • We have several Line IDs of categoryK (Costs, work in process can be created, included in RA).
  • We have several Line IDs of categoryD (Special costs, not included in RA nor in WIP).

For every (I mean every) Line ID we have a separate cost element (cat. 31) assigned.

We created of course OKO6 and KEI1. They are consistent, they are in 1:1 relation in terms of structure assignments and cost elements and Line IDs.

In OKO6 every assignment has its own settlement cost element.

We even included in OKO6 and KEI1 the cost elements (cat. 31), which we actually had to since the system reminded it.

We have separate Value Field for each assignment.

OKG5 (Assignment of Cost Elements for WIP and RA) is carefully designed, all Line IDs has their cost elements.

And everything is working fine except the CO-PA settlement for the line ID of K.

As it turned out, systems clubs together values of line ID category K and allocate to the first Value Field which is associated with category K.

Let’s say I have 3 assignments in OKO6 and the same 3 in KEI1: 10, 20, 30. They have their own Line IDs of K. Each assignment has it’s own Value Field.

Everything goes to the Value Field in assignment 10.

Is this an OSS issue or I’m missing something?

Feel free asking for more clarification.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Aug 04, 2017 at 09:40 AM

    Dear Joe,

    Once RA is performed the accrued values are stored in table COSB and this is the source for the settlement to COPA. So based on the values stored in table COSB and the customizing in tcode KEI3 for the PA transfer structure used for settlement the values will flow to COPA.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      I guess the problem originates at Result Analysis (KKA3) when the system refuses to assign production variance to Line ID PRD despite the fact that there is separate cost element assigned on OKG4 and separate cost elements assigned in OKG5. Instead, loads it to STD. That's what I see in KKA3. And in COSB. So, from here I think, whatever magics I do in the CO-PA transfer structure, the whole stuff will end up in STD.



  • Aug 04, 2017 at 02:51 PM

    Hi Joe,

    Check PA structure source cost element or cost element group cost element assignment. if all 3 cost element is assigned to 1st group?

    may be due to this all 3 line ids cost going to one value field.

    second things, you have separate line ids for each cost bucket, what about technical 31* cost element and assignment to lines ids?as Waman mentioned check COSB table for validation.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      No, as I tried to explain all Line IDs has a separate assignments in OKO6 and KEI1 and they have separate settlement cost element and separate 31 cat. cost elements. The cat. 31 cost elements are assigned to respective assignments too. No mixing, no clubbing. I've just double checked.



  • avatar image
    Former Member
    Aug 07, 2017 at 11:39 AM

    When I do RA analysis I can see that PRD line ID is not updated. I don't know why.

    Add comment
    10|10000 characters needed characters exceeded