Technical Articles
Sales Price Excel Upload in SAP S/4HANA with custom fields
Introduction
This blog is for SD consultants. This functionality can be used from SAP S/4HANA OP2020 FPS0 version. However, it also works with SAP S/4HANA 2021 and 2022 onwards, and SAP S/4HANA Cloud, private edition.
Caution
Although the SAP Standard price communication structures, KOMK and KOMP, has a field which you have already used for your own condition tables, you might not export or import the price data by this Fiori Apps. Because the below 3 settings are needed.
1.Enable Condition Record for Pricing in Sales in the OData APIs
2.Enable Manage Prices – Sales in the UIs and Reports section
3.Enable Template for Importing Condition Record for Pricing in the UIs and Reports section
If you have price condition tables which were created by not using Fiori Apps “Custom fields and Logic”, please test them. If they can’t be updated by the Fiori Apps “Manage Price”, please recreate your own price tables as this Blog described.
Prerequisite
SAP S/4HANA OP2020 FPS00 or upper version. Fiori server must be installed. The user must have “SAP_BR_PRICING_SPECIALIST” role.
Customize
Click Fiori App ID F1481 Custom Fields and Logic.
Push + button to create a custom field.
Business Context: Sales: Pricing Communication Head or Sales: Pricing Communication Item
Set Label, Type and Length as your custom field required.
And push Create and Edit button.
Enable Manage Prices – Sales and Template for Importing Condition Record for Pricing in Sales in UIs and Reports.
Enable Condition Record for Pricing in Sales in OData APIs.
And push Save button.
Push Publish button.
Tr-CD: se11
You can see the custom field was added to the price communication structure automatically.
Tr-CD: segw
Project: SD_PRICING_CONDITIONRECORD
You can see the custom field was added to the odata source automatically.
Customizing
IMG>Sales and Distribution>Basic Functions> Pricing Pricing Control to complete the following tasks:
- Add the custom fields to the field catalog in the Change Field Catalog for Pricing in Sales Customizing activity.
- Create a condition table and add the custom fields to the condition table in the Create Condition Tables for Pricing in Sales Customizing activity.
- Create an access sequence and specify the condition table as an access in the Set Access Sequences Customizing activity.
- Create a condition type and assign the access sequence to it in the Define Condition Types Customizing activity.
- Create a pricing procedure and include the condition type in the Set Pricing Procedures Customizing activity.
- Set the pricing procedure determination for your pricing procedure in the Set Pricing Procedure Determination Customizing activity.
Operation
Click Fiori App ID 4111 Manage Prices.
Set filters and push Go button. Then existing price data appears.
Click Export button.
Then you can get the existing price data in Excel.
Click Download Template button.
You can get the template.
Fill out the price data.
Push import button.
Set the filled template Excel and push import button.
You can see the prices were imported.
Conclusion
You understand how Excel sales price upload works.
Appendix
Help:
Related SAP Blog:
Adding Custom database Field to standard Fiori apps in S/4HANA with Custom Fields and Logic
Adding Field in standard Fiori apps of S/4HANA with Custom Fields and Logic
SAP Note:
2872404 – FAQ: Manage Prices – Sales App
2953452 – FAQ Excel Download and Upload in Manage Prices – Sales App
3067905 – Field control not working in Manage Prices – Sales app
3261750 – Manage Prices – Sales app: Extensibility for standard fields
Fiori Apps Library:
Nice post !
Thansk Kazuhisa for Informative blog.
few more points to know,
Regards
Mandar
Hello Mandar,
Thank you for your information.
Best regards, Kaz
Dear Kazuhisa Iwamoto,
we have this exact requirement, but our Custom field should be linked to a specific data type (e.g. LIFNR in our case) in order to inherit an F4 matchcode on Fiori apps such as "Manage Prices".
We know CFL app allows to create generic data types only, or generic Code List.
We know in some cases we can use SCFD_EUI transaction to enable existing DB fields to be used on CFL, but unfortunately KOMP is not supported as it's a structure, not a Transparent table.
Any suggestions?
Thanks,
(reference: https://blogs.sap.com/2021/01/15/f4-help-for-custom-fields-created-using-custom-fields-logic-inapp-extensibility/comment-page-1/#comment-619223 )
Hello Mateo,
Please follow the below SAP Blog.
Adding Custom database Field to standard Fiori apps in S/4HANA with Custom Fields and Logic
This blog might make non Custom Fields & Logic fields(KOMP fields) to the Custom Fields & Logic fields.
Or add F4 help to your created Custom Fields & Logic fields.
Best regards,
Kaz
Hello Kazuhisa Iwamoto,
thank you for the suggestion. I also found the same blog but as you can see, the first step requires to use SCFD_EUI transaction that cannot see KOMP appended fields because KOMP is a structure, not a transparent table.
Regards,
Hello Matteo,
Then, you need to create F4 match code for a new custom fields you created.
Best regards,
Kaz
Hello Kazuhisa Iwamoto,
so you suggest to create a generic Char10 field with CFL application and then create a custom F4 CDS view that has to be manually linked to that field, without using SCFD_EUI?
Regards,
Yes.
Thank you very much for your help, I'm going to try your suggestions soon.
Regards,
Dear Kazuhisa Iwamoto,
after many attempts we still can't add a custom F4 value help to a custom field (both CFL or manual appended fields) because standard SEGW OData project cannot be regenerated and so Fiori Apps cannot consume the value help.
In-app extensibility allows to extend CDS views by adding new fields and even associations to F4 value help, but value help wont be consumed without regenerating SEGW OData project.
Thank you,