ERP_CO_OLC_E - Messages for Operative Level Costing

The following messages are stored in message class ERP_CO_OLC_E: Messages for Operative Level Costing.
It is part of development package ERP_CO_OLC in software component CO. This development package consists of objects that can be grouped under "".
Message Nr
Message Text
000*** KAIP ***
001System error: order operation with invalid internal number &1 &2
002Order or operation &1 &2 does not exist
003Order &1 requires assignment to an operation number
004Order &1 cannot be assigned to an operation number
005System error: order operation with invalid internal number
006For OAA, summarization on 'Object number' is forbidden (profile &1)
007Operation and activity cannot be entered at the same time
008No order given for operation &1
009Cannot read ILOA data &1
010Order &1 does not exist
012'&1' on sub-operational level &2 &3 not possible
013'&1' on sub-operational level &2 &3 &4 not possible
019Refurbishment Order Indicator not allowed for order type &1
020Operation account assignment not allowed for this order &1
021Operation account assignment not allowed for networks
022Business transaction not supported for operation account assigned order
023Operation &1 has Actual Costs. Deletion not allowed.
024Historical order from operation account assigned order type not supported
030*** SETTLEMENT ***
031Operation &1; not relevant for costing
032Operation &1 / &2; settlement rules not supported for suboperations
033Settlement profile &1; default receiver object type is not defined
034Settlement profile &1; default value for allocation structure is missing
035Settlement profile &1; maximum number of distribution rules not defined
036Order &1 already closed
037Order &1 locked
038Order &1; maintenance of settlement rule not allowed
039Order &1 is not operation level costed
040Order &1; error on settlement rule creation
041Operation &1; settlement rule does not exist
042Refurbishment orders are not supported for Operation Account Assignment
043Investment orders are not supported for Operation Account Assignment
044Operation &1; error on settlement rule creation
045Errors on settlement rule creation occurred; see log
046Settlement rules for operations created
047Distribution rule for operation level cost orders not supported
048Settlement rules are missing; see log
049No source structure defined for operation &1/&2; adjust rule manually
050In operation &1 source assignment &2 does not exist; adjust rule manually
051Materials not allowed as settlement receivers for OAA orders
052Operation & has no costs
053Only existing settlement rules processed; no data changed
054No operation selected, or selected operation is a suboperation
055Info messages occurred during settlement rule creation; see log
056Operation & has no commitments
057No entries in the settlement rule creation log
058
059Operation &1; receiver in settlement rule determination is wrong (&1 &2)
060Operation &1; settlement rule determination not defined (&2 &3)
061Settlement to operation account assigned orders (&) not allowed
062Operation &1; error at the settlement rule determination (&2 &3)
063Operation &1 / &2: Settlement rule already exists
064Order &1/&2 cannot be created as OAA order and investment order at once
066Operation Account Assignment orders (order type &) are not supported.
067Account assignments are missing; see log
068Order of type &1 for plant &2 cannot be changed due to consistency issue
069Not possible; operation &1 has been deleted
080*** Budgeting, Investment Management ***
081Order with cap.inv.prog.position and WBS element in operation not allowed
082Orders with project assignment in operations cannot be budgeted
083No entries in the account assignment creation log
084Operation &1; settlement rule determination (&2) failed; receiver missing
085Commitment carryforward not possible on single order operation level
100There are no Cost Objects for the Selected order(s).
110Settlement rules not copied; different account assignment settings
800*********************for BAPIS, RFC and services
801Operation &1 in order &2 could not be found
Privacy Policy