About BADI_FINS_SUMMARIZE_BSEG

[ISHIMOTO]

Hi,

The following error occurs when linking to CFIN from public cloud

　　Text:Source document <company code> <document No> <FY> not posted due to inconsistent summarization
　　Message No. :FINS_CFIN_AC_DOC 025

We received a response from SAP that the following BADI implementation is required to resolve the error.

BADI_FINS_SUMMARIZE_BSEG

Since we don't want to summarize BSEG, returning a blank to the below will not fix the error.
How can we use this BADI to avoid summarizing BSEG?

abap_false = ''.

eb_summarize_to_the_max = abap_false
eb_summarize_acct_assignment = abap_false

[OwenLiu]

Informed expert.

[jan_roenner · Accepted solution]

Hi,
The point is, that CFIN requires that BSEG line items are created with the same granularity like in the source system. If the system rejects a posting with Error FINS_CFIN_AC_DOC025 it is required to summarize BSEG (at least as much as in the source system). The easiest and safest way is implementing BADI_FINS_SUMMARIZE_BSEG.
If you don't want to summarize BSEG implementing this BAdI doesn't make sense at all because it would have the same effect like setting 

eb_summarize_to_the_max = abap_false
eb_summarize_acct_assignment = abap_false

Why do you want to avoid BSEG summarization? (Also summarization "to the max" would never result in less BSEG items than in the source system, because BUZEI_SENDER is never affected by summarization.)
Typically all reporting on related fields is based on ACDOCA which won't be affected by BSEG summarization at all.

Please also consider latest version of CFIN-FAQ SAP Note 2184567 Point 45 "How do I need to set up document summarization settings?" considering its latest version.

Best regards
Jan

[ISHIMOTO · Accepted solution]

Thank you for your comment.

The user requirement is to link to CFIN without summarizing BSEG.

However, SAP has responded that implementing BADI_FINS_SUMMARIZE_BSEG is required to avoid errors. (Message No. :FINS_CFIN_AC_DOC 025)

So I would like to know how to implement BADI_FINS_SUMMARIZE_BSEG without summarizing BSEG.

Regards,

[marlene_katzschner · Accepted solution]

Hi

[HenrikeGrtecke · Accepted solution]

Hello, thank you for your question. It has been forwarded to the experts. Have a seen this blog? https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/999-the-number-of-the-bseg/ba...? Kind regards, Henrike

[TomohiroOono · Accepted solution]

Thank you for your comment.

I would like to add to Ishimoto's question.

Instead of implementing BADI_FINS_SUMMARIZE_BSEG, we are trying to avoid the error by matching the OBCY setting in the S/4HANA public cloud with the OBCYX setting in C-Fin.

Are the C-Fin OBCYX settings correct?

Reference transaction -> Reference transaction for OBCY in S/4HANA public cloud

Type -> Journal entry type of the voucher in error

Company Code -> Company code of the voucher in error

Table Name -> Table name of OBCY in S/4HANA public cloud

Field Name -> Field name of OBCY in S/4HANA public cloud

Thanks & Regards,

[marlene_katzschner]

Hi,

let me add some additional comment to Jan's reply.

As you mentioned your S/4HANA Public Cloud FI document could not be posted in the CFIN system. Reason was that in the public cloud there is a default BSEG summarization active. This summarization is cannot be configured using the transactions OBCY/OBCYX. Nevertheless you have to ensure that the document has the same number of lines (BUZEI) as in the source, otherwise you will get the error. We from standard development suggest to implement the BAdI in a way that for your public cloud source systems the maximum BSEG summarization is always active. (this can be achieved by implementing the BAdI BADI_FINS_SUMMARIZE_BSEG to return always "X" for your cloud systems). There might be customer specific solutions to achieve a summarization as in the source, but we from standard strongly recommend the BAdI. (This is also document in our CFIN FAQ note and in the online help for the CFIN integration).

Why does the implementation of the BAdI not "disturb" reporting etc.? As Jan mentioned, the BUZEI is always a split criteria for the document summarization. The standard reporting is using ACDOCA where you still have all attributes which are removed from BSEG. So we do not see an issue, that why we recommend this approach.

Before you invest in your customer specific solution, I would suggest to implement the BAdI first to check if there is really an issue.