Skip to Content

This blog is a continuation to the earlier blog “SD-FI-COPA reconciliation: Part-1”

This blog talks about how characteristic and value field flow is integrated between SD and COPA and if something went wrong in COPA document how to regenerate correct values without impacting respective SD and FI postings.

T-code KE4S can be used to simulate the characteristic and value field flow from SD to COPA or reverse and re-post COPA document alone. Alternatively,

T-code KE4ST can be used only for simulation purpose. Let us see how this can be used to understand the integration between SD and COPA without running through configurations.

Important fields in selection screen (KE4S):

Test Run:

No document is created (Even in posting run). Only values are simulated.

Create Log:

If we select this, Characteristic and value flow log is created for further analysis.

Redetermine profitability segment:

This option should be used cautiously. If this is selected, profitability segment values are redetermined as per the current system config. This can be used in scenarios like, incorrect values posted in profitability segment due to incorrect derivation rules/incorrect logic in user exit.

Check for existing records:

This performs a pre-check before transferring the data. Only documents which have not been flown to COPA are considered for posting.

Reversal of line items:

This option reverses already transferred documents and re-post all (Both transferred and non-transferred).

Posting without check:

This option should be used cautiously. This option re-post everything. If there are documents already posted, system posts duplicate document.

Please go through F1 documentation of each field for more details.

Go to T-code KE4S, enter a billing document which was transferred to COPA and execute.


Below is the output of report.


We can see two lines are created here because, one is for reversal and other is for re-post. There are different status ICONs in ALV tool bar indicating number of documents in respective status. This helps particularly when we process huge number of documents.

Now let us see how characteristic and value flow analysis is done.

Characteristic flow analysis:

Select the row and click on “characteristics”.


Below screen shows the characteristic values that are derived in COPA document.


Click on “Display derivation analysis”.

In this step, we can find how each characteristic was modified in each step of derivation with respective old and new values. If any characteristic is changed in a particular derivation, that row is highlighted in yellow. Node “Values before/After” just displays old and new values during derivation process.



Derivation customization can be configured in t-code KEDR.

Value flow analysis:

Select the row and click on value flow.


Below result shows, source of each value field. As I mentioned in my previous blog, COPA value fields are linked to sales pricing conditions.

So, below output analysis shows how each sales condition is transferred to the respective COPA value field.


You can see for some rows, there is no G/L account assigned. It is because, these conditions are configured as “Statistical” and hence, no FI posting.

Since there is no FI posting, no G/L determined here too. We can find the statistical tick in the pricing conditions of the original billing document. Such kind of config is required when we want to see some figures only in reporting/for analysis purpose but not part of financial booking.

In first row, Currency type B0 indicates values in “Operating concern currency” and 10 stands for values in “Company code currency”.



COPA valuation is used for automatic calculation of values in costing based COPA (Both planned and Actual). There are different valuation strategies provided by SAP.

  1. Valuation using material costing,
  2. Valuation using conditions and a costing sheet,
  3. Valuation by means of a user-defined program exit,
  4. Valuation with transfer prices

Please check below IMG documentation for more details.



Select the row and click on valuation.


Each valuation strategy step can have different logic to change value fields.


Click on the Analysis button which show if the value field has been changed in respective user exit.


Click on “Result of Valuation”. This shows the entire list of value fields before and after valuation.


Hope this blog helps to give better understanding of SD-COPA integration and how characteristics and value fields are determined.

Your valuable feed back on this blog is most welcome 🙂



To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member

    Good information. Thanks for sharing Vinod. if your familiar about operating concern ceration pls share useful stuff on it. as BW consultant very interested know FI stuff


    1. Former Member Post author

      Thanks Rama. Sure. Will do that in couple of days. As year end is approaching, would be packed up for next 2 months 😥



  2. Ranu Eugene

    Hi Vinod,

    Much awaited part two doc is out. 😉

    Must say very useful document.

    Please do keep sharing.

    Keep up the good Work 🙂 .

    Best of Luck. 🙂



  3. Former Member

    Hello Vinod,

    Very helpful doc and a very  valuable one. Expecting more contributions from your end in futute also.Thanks alot for sharing ur knowldge.


    Lakshmi S

  4. Former Member Post author

    Thanks a lot Satya, Murali, Daniel, Swapnoneel 🙂

    It’s a pleasant surprise to see Thought leader badge for this content 😆

    November seems to be a great month for me both personally and professionally 😉



  5. Former Member

    Thanks Vinod…. good analysis and very helpful to me.

    please can you explain in what cases uses the user exit in valuation and how to config?

    awaiting for your answer.

    best regards

    Siva Ram

    1. Former Member Post author

      Thanks Sivaram 🙂

      Exits are used when you need your custom logic to redetermine the value field value. As I have shown in the image, we should assign the exit name in configuration (For eg.U01) in t-code KE4U.

      SAP has delivered enhancement COPA0002 (t-code CMOD) and function module EXIT_SAPLKEAB_001 for writing our custom logic. Implement your logic in user exit include program ZXKKEU03.

      This exit is triggered for each value field (if any exit name is assigned to it in KE4U). Use ABAP statement CASE EXIT_NR. and write your logic for the respective field.

      Exporting parameter ep_target  can be used to update the respective value field based on custom logic.

      Also, you can use this exit to perform any custom validations and issue warning/error messages.

      Please let me know if you need any further help.


      V V


Leave a Reply