Loading
Industries Order Management
Table des matières
Filtrer par (0)Ajouter
Sélectionner des filtres

          Aucun résultat
          Aucun résultat
          Voici quelques conseils de recherche

          Vérifiez l'orthographe de vos mots-clés.
          Utilisez des termes de recherche plus généraux.
          Sélectionnez moins de filtres pour élargir votre recherche.

            Recherchez dans toute l’aide de Salesforce
            Recherchez dans toute l’aide de Salesforce
            Rules for How Point of No Return (PONR) Propagates through a Decomposition Plan

            You are here:

            1. Salesforce Help
            2. Docs
            3. Industries Order Management

            Rules for How Point of No Return (PONR) Propagates through a Decomposition Plan

            This topic provides an overview of how the PONR feature works in a decomposition plan.

            Once an order item has reached the PONR, it generally cannot be canceled or amended, unless you have selected the Force Supplementals option for that order (see Allow Supplemental Changes after PONR (Point of No Return)). But in some cases, you can still cancel or amend other order items in the same order. This topic explains which items can and cannot be canceled or amended after an order item has reached the PONR.

            Note
            Note

            This information is relevant for Spring '20 and later. If you're using an earlier version of Order Management, then no part of the order can be canceled or amended when any item reaches the PONR.

            When an orchestration item that is marked as PONR moves to a Running state, then the following state changes occur:

            • The order items that are linked to the PONR orchestration item are marked as PONR.

            • All upstream order items are marked as PONR, all the way to the root order item.

            • All children of the root order item, and their children, are marked as PONR.

            Note: This means that every bundle will be either past the PONR or not. There's no case in which only some items in a bundle can be canceled or amended. If every root order item is past the PONR, then the order itself is past the PONR, and no part of it can be canceled or amended.

            Example of PONR in an order

            The following workflow shows a simple order with two order items (Mobile line and Digital TV), neither of which have yet reached the PONR.

            A simple chart showing the relationships between orchestration items

            Now we'll say that the orchestration item associated with Activation Item has reached the PONR. Immediately, Activation Item is marked as PONR, and so are several other items as shown below:

            A chart showing that when certain items reach the PONR, it means that you can longer change items in that item's hierarchy.

            The entire bundle Mobile line has reached the PONR and cannot be canceled or amended.

            Here's what has happened:

            1. Activation Item reached the PONR.

            2. Because Activation Item reached the PONR, the upstream item (Mobile Activation Specification) reached the PONR.

            3. Because Mobile Activation Specification reached the PONR, the upstream root item (Mobile Line) reached the PONR.

            4. Because Mobile Line reached the PONR, its child (VAS) reached the PONR.

            5. Because VAS reached the PONR, its child (Data Roaming) reached the PONR.

            Digital TV has not reached the PONR and it can be canceled or amended, even though other items in the order cannot be canceled or amended.

             
            Chargement
            Salesforce Help | Article