In CE2208 and CE2302, a new Fiori App 'Manage Sales Contracts - Version 2'(F5987) is provided in SAP S/4AHANA Cloud, to allow you to process the sales contracts. In this blog, you will know the main functionality of this app and some key features.

Figure 1:Manage Sales Contracts - Version 2
Business Context
As an internal sales representative, he/she wants to manage the sales contracts like creating new sales contracts or changing some key information. Compared to the old 'Manage Sales Contracts', he/she has to do such processes in the traditional UI, and now he/she can process the contracts in pure Fiori UI. and it's highly improved the user experience.
Scope
The below diagram shows the enabled operations on each entity layer, only the Quantity Contract and Value Contract are allowed to be processed.
Please note: the allowed contract types are pre-defined by SAP as the default setting.
Entity |
Read |
Created |
Header |
X |
X |
Header Partner |
X |
X |
Header Text |
X |
X |
Header Pricing Element |
X |
X |
Ship to Party |
X |
|
Item |
X |
X |
Item Partner |
X |
X |
Item Text |
X |
X |
Item Pricing Element |
X |
X |
Item Billing Plan |
X |
X |
Item Billing Plan Item |
X |
X |
Some actions are applied from this application:
Sales Contract Header |
Display |
Update Prices |
X |
Set/Remove Billing |
X |
Change Ship-to Party Data |
X |
Incompleteness Info |
X |
Sales Contract Item |
Display |
Update Prices |
X |
Set/Remove Billing |
X |
Set/Remove Rejection Reason |
X |
There are some reused actions are provided for all sales documents, they are enabled in Manage Sales contracts as well:
- Attachment: Showing the document-related attachments.
- Change Document: Showing the change log for a specific sales contract.
Highlighted Features
In CE2302, there are some new key features within this application, which can help user to realize particular business scenarios.
Billing Plans in Sales Contract Items
Billing plans are used for milestone billing and down payments in
Quantity Contracts. The system determines from the item category whether a billing plan is enabled and, if so, which type of plan. To enable the billing plan for an item, change the item category to
CKMN. Then you can create, display, and edit the billing plan on the item detail page. And item category is the only criterion to enable the ‘Billing Plan’ tab on the item object page.

Figure 2:Item Category for Billing Plan

Figure 3:Billing Plan on Item
For more information about billing plan in general, see
Billing Plans.
For more information about down payments, see
Down Payment Processing for Sales Contracts.
Sales Contract Fulfillment Rate
The sales contract fulfillment rate indicates the consumption of the sales contract by creating the subsequent sales orders, as the sales order are created per sales contract items, therefore the fulfillment rate is tracking the sales order per sales contract items.
On top of the item object page, there is a data point name ‘Fulfillment Rate’ to show the rate of total consumed Quantity or Value for this item, which helps the user realize the progress of a sales contract item.

Figure 4:Sales Contract Fulfillment Rate
Quantity Contract and Value Contract
The Quantity Contract and Value Contract are both supported in this app, and the backend can identify this contract type only by the ‘Completion Rule’ on the item category configuration, so before an item is initialized, no contract type can be determined. This caused the input field to be not available till the item instance is created by pressing the ‘Enter’ button(or other UI reaction).

Figure 5:Combined column for Target Quantity or Value
After initializing the item, 'Target Quantity' or 'Target Value' will be available respectively.

Figure 6: Target Value of item
Constraint
There are some Limitations due to technical reasons for contract partners listed in below:
- Limitation for contract specific partner types: ‘AA’ and ‘AW’
These kinds of partners can’t be created from the UI on the header and can’t be shown in the item partner table.
- Limitation for search/filter fields comes from associations
As the new app is built on a new framework and considered the performance reason, fields from the associations are not supported for search and filter as of now. E.g. SoldtoParty Name.