Question Re: Market Segment Planning using Extension fields with B... in Enterprise Resource Planning Q&A

Market Segment Planning using Extension fields with Business Context "Accounting: Market Segment"

suyoung_choi3 — Tue, 09 Sep 2025 02:39:16 GMT

Hi all,

I added Custom fields "YY1_SalesTeam" for the Market Segment Report.
I want to use Custom fields to upload Market segment planning data in Import Financial Plan Data App.
A message appears saying that the field is invalid and the upload fails.
How can I upload Market segment planning data using Custom fields "YY1_SalesTeam"?

Thank you

Su Young

Re: Market Segment Planning using Extension fields with B...

Chris1973 — Tue, 09 Sep 2025 05:25:39 GMT

Hello @suyoung_choi3

Thank you for your email.

To enable you upload Market Segment planning data you must ensure that the field is correctly extended and configured for plan data import. People commonly encounter issues that include technical name mismatches and unsupported business contexts or when there is a lack of proper alignment of plan and actual data for CO-PA because this uses different suffixes. If the technical name does not include the correct suffix or is not released for planning, SAP will treat it as invalid and fail the upload.

You can fix this through Field Extension for Planning. For that go to the Custom Fields and Logic app and check that YY1_SalesTeam is released for the planning business context. If the field is only released for your actuals and not for the plan data, then re-create or adjust it and make sure Planning is enabled during the setup.

Ensure the chosen technical name and suffix is correct. You should check the template downloaded from the app, make sure the field matches the technical that is required by SAP. For the custom characteristics, the correct name often ends with a plan-related suffix.

Ensure you date format and template is correct. For this download the planning data template directly from the Import app F1711, make sure you use SAP’s recommended separators. Then map the columns exactly as shown in the template. Do not alter the fields that are mandatory.

See the following links for more details.

See SAP KBA 3427462

CO-PA Planning with Custom Fields

https://userapps.support.sap.com/sap/support/knowledge/en/3427462

Best regards

Chris

Re: Market Segment Planning using Extension fields with B...

Susanne_Helbig — Tue, 09 Sep 2025 13:36:44 GMT

Dear @suyoung_choi3,

you might have missed to enable the usage for the following APIs as described in our docu Creating Custom Fields in SAP S/4HANA Cloud System, point 4.

API_FINANCIALPLANDATA_SRV
API Financial Planning Entry Item

Can you please check and correct this setting and let me know if this solved your issue?

Best regards
Suanne

Re: Market Segment Planning using Extension fields with B...

suyoung_choi3 — Tue, 09 Sep 2025 23:53:26 GMT

Thank you for your reply. The APIs you mentioned are enabled.

Re: Market Segment Planning using Extension fields with B...

Susanne_Helbig — Wed, 10 Sep 2025 07:46:58 GMT

Dear @suyoung_choi3,

I kindly ask you to create an SAP incident on component CO-FIO-OM-PL for this.

Kind regards
Susanne

Re: Market Segment Planning using Extension fields with B...

suyoung_choi3 — Tue, 16 Sep 2025 02:31:28 GMT

Referring to the "https://help.sap.com/docs/SAP_S4HANA_CLOUD/1cbcff7ccd35405ab445b223c1ab1588/be523cf4c45940b6a915162161c39340.html" site, it seems that the Extension Fields for Upload are extension fields using the business contexts JEI (journal entry item) or COB (coding block). It seems that the Extension field using "Business Context Accounting: Market Segment" is not supported.

Re: Market Segment Planning using Extension fields with B...

suyoung_choi3 — Tue, 16 Sep 2025 07:30:49 GMT

Dear ALL,

I found that the Extension field using "Business Context Accounting: Market Segment" must end with the suffix _MSE, as shown in the example below.

YY1_newfield_MSE

Thank you

Su Young.