SAP Knowledge Base Article - Public

3581003 - FAQ: Release for Delivery (R4D) - Public Cloud Edition

Symptom

FAQ for Release for delivery APP.

DISCLAMER: Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Environment

  • S/4 Hana Cloud Public Edition
  • Advanced ATP
  • Release for Delivery

Resolution

1. The R4D worklist is not being refreshed with new orders or you find some inconsistencies displayed, why?

  • Unassign all user IDs from the order fulfillment responsibility worklist, SAVE and re-create the assignments of user IDs to the order fulfillment responsibility worklist! This procedure will force the regeneration/rebuild of the R4D worklist.
  • The order/material is already assigned to another worklist.
  • The R4D worklist has been created in the past and some order(s) have been delivered meanwhile - however this order is still being displayed? -> click on refresh button (right next to the search bar) or rebuild the worklist completely (see first point).

2. The confirmation quantity of an order item cannot be modified/changed/is not editable. Why?

  • An order item cannot be changed in R4D if one of the following statements is true:
      • order item is from fashion industry (segmentation is active)
      • order item has a special procurement key (SOBKZ)
      • order item has multiple requested schedule lines 
      • order item is part of a delivery group
      • order item has product allocation check (PAL) active (an information message is displayed in the APP - PAL related orders can be be delivered)
      • order item has alternative based confirmation(ABC) active (an information message is displayed in the APP)
      • order item is part of a sales BOM
      • order item is an STO - R4D cannot handle confirmation changes that would influence the availability at another plant that is also part of the user's worklist.

3. Role "SAP_BR_ORDER_FULFILLMNT_SPCLST" was assigned to my user ID, but I cannot access the "release for delivery" APP. Why?

  • Reason: Missing license: to use Release-for-Delivery the following scope item is needed: "1JW" - SAP S/4HANA Cloud advanced supply chain - Material ID (8005593).

4. Not all materials are displayed in the R4D APP. Why?

  • R4D can just displayed 100 material/plant combinations (on each tab). There are plans to remove this limitation someday in the future. Please recheck the order responsibility settings and reduce the amount of materials-plant to be processed (lower than 100).

5. The performance of the R4D APP is bad. Any hints?

  • Release for Delivery is not designed to process a high amount of material-plant combinations – with each additional material plant combination, significant performance costs can be observed – regardless of how many requirements are actually belonging to this material plant combination. Recheck the order responsibility settings and reduce the amount of materials/plant to be processed. R4D APP was designed to MANUALLY process the most important orders/materials.

6. What is the explanation for the "impact bar"?

  • The "impact bar" displays a percentage value - based on the order net value of all requirements for that material. This means: the system calculates an average value for all materials and displays the impact value based on the average. A high impact value indicates, that this material has the most valuable order requirements!

7. Can we have additional selection criteria (like in BOP, e.g. order type) for the order selection?

  • The design of R4D functionality does not support any other selection than via material/plant (MARC). That ensures that two processors do not share/assign the same "available" quantity. There would be always a conflict between the two processors - who can deliver the requested quantity to his customers.
  • It is planned to enhance the R4D filter functionality (e.g. to exclude credit or delivery blocked orders) within one of the future releases (release date unknown).

See Also

KBAs

3540460 - FAQ: Backorder Processing (BOP) with advanced ATP - S/4HANA Public Cloud Edition
3484545 - FAQ: Advanced ATP with S/4 Hana Cloud Public Edition
3381688 - FAQ: Alternative based Confirmation (ABC) with aATP - S/4HANA Public Cloud Edition
3193069 - All knowledge resources for aATP on SAP S/4HANA Cloud
2563519 - SAP S/4HANA Cloud - How to create the perfect incident

Keywords

Freigabe; Lieferung; Error; Refresh; Delivery; , KBA , CA-ATP-IRP-2CL , ATP: Interactive Requirement Processing (RFDY) (Public Cld) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions