CRMS4_SOLO_ORC_LOG - Solution Order Orchestration Logging related messages
The following messages are stored in message class CRMS4_SOLO_ORC_LOG: Solution Order Orchestration Logging related messages.
It is part of development package CRMS4_SOLUTION_ORDER_ORC_LOG in software component CRM-S4-SOL-SLO. This development package consists of objects that can be grouped under "Solution Order: Orchestration Logging".
It is part of development package CRMS4_SOLUTION_ORDER_ORC_LOG in software component CRM-S4-SOL-SLO. This development package consists of objects that can be grouped under "Solution Order: Orchestration Logging".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4. |
| 001 | The execution of the &1 adapter has started. |
| 002 | The execution of the &1 adapter has been completed. |
| 003 | &1 adapter is triggered with the &2 scenario. |
| 004 | Sales order creation is already in progress for the solution order &1. |
| 005 | The pricing data is set to empty in sales utility. |
| 006 | The orchestration status &1 is set to &2. |
| 007 | The distribution status is set to &1 for the item &2. |
| 008 | Goal API access creation has failed. Check the messages on UI. |
| 009 | Item status set as &1 for the item &2. |
| 010 | Item &1 is grouped with &2 to create/update the follow-up document &3. |
| 011 | Item &1 is invalid for orchestration as the item status is &2. |
| 012 | Item &1 was already considered for orchestration. |
| 013 | Sales order &1 is created. |
| 014 | AIF message with the message guid: &1 has changed. |
| 015 | Item &1 is valid. The orchestration process will begin now. |
| 016 | Item &1 has valid changes to be updated to its follow-up document. |
| 017 | The execution of the &1 adapter has started with the &2 scenario. |
| 018 | Invalid data for the &1 adapter. Hence the execution is terminated. |
| 019 | CRM_ORDER_SAVE is triggered from the &1 adapter. |
| 020 | Exceptions are raised. Hence CRM_ORDER_SAVE has failed. |
| 021 | Subscription API payload structure received from solution order is empty. |
| 022 | Exceptions are raised from the POST request. Check the AIF log. |
| 023 | Subscription Billing API is triggered with a POST request for the item &1 |
| 024 | The execution of the POST request is successful for item &1. |
| 025 | POST request execution has failed for item &1 due to &2. |
| 026 | Subscription item &1 is not valid for simulation. |
| 027 | Response data from the POST request is mapped to 1O data structures. |
| 028 | Response data from the POST request is not mapped to 1O data structures. |
| 029 | CRM_ORDER_SAVE is triggered from the process class. |
| 030 | Goal API access is not opened. Check the messages on UI. |
| 031 | Item &1 is grouped with &2 for &3 scenario. |
| 032 | The execution of the CRM_ORDER_SAVE is successfully completed. |
| 033 | Partner function &1 cannot be saved. |
| 034 | An exception is raised while creating/updating the &1 entity. |
| 035 | Solution order &1 is locked. |
| 036 | Execution failed due to incomplete fields. Check the messages in UI. |
| 037 | No reference found for the solution order &1 in the VBAK table. |
| 038 | No item text found in the solution order &1 |
| 039 | Mapper mode is set to &1. The follow-up document &3 will be &2. |
| 040 | Item &1 is not valid for orchestration. |
| 041 | Item &1 is invalid for orchestration. |
| 042 | Execution failed due to incompletion log, please check the messages on UI |