App Monitor Down Payment for Purchase Order.
Create Down Payment Request.
If you maintain the down payment on header level, there is no value proposed for the down payment or the down payment request.
S/4 HANA Cloud
This is due to the fact, that the down payment on header level is not split onto the item levels. It does just mean that for the whole PO
a down payment of the given amount is expected. This down payment can be created for any of the items or distributed however needed/wanted to the different items. If you want to have a proposed value in " create Down payment request " you have to define the down payment on item level in the PO.."
When the PO is saved with a header and item DP requirement the values maintained are written to the down payment fields in EKKO and EKPO (EKKO/EKPO-DPAMT) . The Monitor App just displays those value directly from the DB tables.
When you select the option to create a down payment in the Monitor App, the system does not look at the header value at all, if you choose the header line the system will always propose an empty value which would have to be maintained manually. Only when you choose to create a DP at the item level will the system pick up the amount maintained as you have pointed out. This is the design the DP is designed to function at the item level. It is possible to create a DP at the header level but there is no correlation between the
header down payment values and the item, this is not developed.
So if you want to use a general header down payment you can maintain it manually in the PO and during the DP create you can manually maintain the value you want to post as a down payment.
KBA , MM-FIO-PUR-PO , Fiori UI for Purchase Orders , Problem