OverviewIn this blog post, we will show how to add an additional section called Custom Fields to the Manage Sales Orders - Version 2 app. This section appears dynamically based on the sales order data. For this blog post, we will use the sales organi...
If you integrate SAP S/4HANA Cloud with an SAP on-premise solution and APIs don't work for your specific scenario, you can use a limited set of Business Application Programming Interfaces (BAPIs).For more information about using BAPIs, see this blog ...
You might want more fields from master data available in your sales documents, for example, to display in a sales order app or to print in the sales order confirmation. You can do this with key user extensibility.You can find detailed information abo...
Do you want to know how to better adapt the standard sales processes to your business needs? If yes, check out the following document that covers the basics of key user extensibility for Sales in SAP S/4HANA Cloud:
Key User Extensibility in SAP S/4H...
Hi @SriSaiBhargav,You did everything correct so far. You can only create Custom Fields on Sales Document level which includes Quotations, Orders, Customer Returns etc.. To copy the value of a custom field from one sales document to another sales docu...
Hi @Rajvardhan_P,It looks like your coding is not executed. Have your registered your implementation in the configuration UIs Define Custom Routines for Data Transfer to Billing Documents (ID: 102865) and Copying Control for Billing Documents Set Sta...
Hi @krishna_ABAP ,I just tested in our system and it was working as expected with the following coding:Maybe you missed to add the sales order number to the variable lr_item_ext->key ? REPORT zsd_bapi_extensibility.
DATA lo_bapi_mapping TYPE REF TO ...
Hi @Dmitry_K,At the moment you cannot retrigger pricing automatically in S/4HANA Public Cloud. There is already a customer influence request for that requirement. Please vote for it and leave some comment to get the requirement prioritized.https://in...
Hi @trowbste,This is not a bug in the OData V2 Service. In OData V2 Service for Sales Orders you need to use the language-dependent keys for partner function. Your issue is exactly the example in the documentation. If your logon language is english, ...