/ACCGO/OE_MSG - Messages for Orchestration Framework
The following messages are stored in message class /ACCGO/OE_MSG: Messages for Orchestration Framework.
It is part of development package /ACCGO/OE in software component LO-AGR-LDC. This development package consists of objects that can be grouped under "ACCGO: Orchestration Framework".
It is part of development package /ACCGO/OE in software component LO-AGR-LDC. This development package consists of objects that can be grouped under "ACCGO: Orchestration Framework".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Actual qty should be less than or equal to scheduled qty |
| 001 | Actualization completed for ticket key &1 |
| 002 | No records found for passed AI and calling application |
| 003 | Error during CIP processing |
| 004 | Error during checks |
| 005 | Error while locking nomination |
| 006 | Error while reading nomination |
| 007 | Error while CIP processing read |
| 008 | No document generated |
| 009 | Ticket is already actualized; no error log exists |
| 010 | Ticket is in Error Status/In Process, Please click Error Log Button |
| 011 | Select a row |
| 012 | Multiple row selection not possible |
| 013 | No navigation possible |
| 014 | No junction function configured |
| 015 | Record not found |
| 016 | No movement scenario found |
| 017 | Ticket is locked |
| 018 | No data found |
| 019 | Error while locking ticket |
| 020 | Update flag in error log is not updated properly |
| 021 | No order found to create delivery |
| 022 | Configuration changed; sequence number not found |
| 023 | Error while converting the ticket key into internal format |
| 024 | Error while reading the sales order document |
| 025 | Ticket &1 is already actualized; re-execution not possible |
| 026 | Inter/Intra company could not be determined |
| 027 | No specific material determined |
| 028 | Title transfer not determined |
| 029 | Incoterm not found |
| 030 | &1 document &2 created |
| 031 | Inbound delivery &1 &2 has enough open quantity |
| 032 | Inbound delivery &1 &2 and Purchase Order &3 &4 are linked |
| 033 | Order &1 &2 is called-off against contract &3 &4 |
| 034 | All documents are linked |
| 035 | Purchase Order &1 &2 is not called-off against contract &3 &4 |
| 036 | Purchase Order &1 &2 and inbound delivery &3 &4 are not linked |
| 037 | Inbound delivery &1 &2 does not have enough open quantity |
| 038 | Order &1 &2 linked to inbound delivery &3 &4 found |
| 039 | Called-off contract found for the Purchase Order &1 &2 |
| 040 | No order found for given inbound delivery &1 &2 |
| 041 | No linked order found for the inbound delivery &1 &2 |
| 042 | The re-execution of the ticket &1 started from the recovery report |
| 043 | The re-execution of the ticket &1 is done from the recovery report |
| 044 | LDC update from OF failed |
| 045 | Error in application document creation |
| 046 | Purchase Order &1 &2 does not have enough open quantity |
| 047 | Order &1 &2 and contract &3 &4 passed are linked |
| 048 | No delivery found for given order |
| 049 | Scenario is inter/intra company |
| 050 | Specific material determined for material &1 |
| 051 | Title transfer &1 determined |
| 052 | &1 is a valid vendor |
| 053 | Application document &1 created |
| 054 | Ticket key &1 created from OF Framework. |
| 055 | Outbound delivery &1 &2 has enough open quantity |
| 056 | Sales Order &1 &2 and outbound delivery &3 &4 are linked |
| 057 | Outbound delivery &1 &2 does not have enough open quantity |
| 058 | Sales Order &1 &2 and outbound delivery &3 &4 are not linked |
| 059 | Sales Order &1 &2 is called-off against contract &3 &4 |
| 060 | Sales Order &1 &2 has enough open quantity |
| 061 | Sales Order &1 &2 does not have enough open quantity |
| 062 | Sales Order &1 &2 is not called-off against contract &3 &4 |
| 063 | No called-off contract found for Sales Order &1 &2 |
| 064 | Order &1 &2 linked to outbound delivery &3 &4 is found |
| 065 | Linked contract found for Sales Order &1 &2 |
| 066 | No linked order found for outbound delivery &1 &2 |
| 067 | Purchase Order &1 &2 has enough open quantity |
| 068 | No called-off contract found for Purchase Order &1 &2 |
| 069 | No called-off Purchase Order found for contract &1 &2 |
| 070 | No logistical TC found for the order &1 |
| 071 | Cannot create ticket for LDC ID &1 |
| 072 | Ticket created for LDC ID &1 |
| 073 | Error during call-off |
| 074 | Header/status data not found for delivery &1 |
| 075 | Item data not found for delivery &1 |
| 076 | POD execution failed for delivery &1 |
| 077 | Material doc &1 for POD has been created |
| 078 | Nomination confirmation ticket &1 created |
| 079 | Nomination confirmation ticket &1 created with actualization error |
| 080 | Nomination confirmation ticket could not be created |
| 081 | Purchase Order &1 is locked |
| 082 | Sales Order &1 is locked |
| 083 | Return Sales delivery |
| 084 | Purchase Order &1 &2 is not marked for return |
| 085 | Application mode is manual |
| 086 | Application mode is automatic |
| 087 | Application type is contract |
| 088 | Pricing trading contract found |
| 089 | Scenario is carlot relevant |
| 090 | Contract &1 &2 has enough open quantity |
| 091 | Application type is not contract; go unassigned |
| 092 | No best fit contract found |
| 093 | Automatically Split rule result is 'Yes' |
| 094 | Automatically Split rule result is 'No' |
| 095 | No data found for nomination &1 item &2 |
| 096 | Contract &1 &2 does not have enough open quantity |
| 097 | No function group determined; no ticket created |
| 098 | Grades are not maintained for the material |
| 099 | LDC ID did not return any details |
| 100 | Called-off contract &1 &2 found for the order &3 &4 |
| 101 | Call-off process from OF started |
| 102 | No linked delivery found for the order &1 &2 |
| 103 | Order &1 &2 does not have enough open quantity |
| 104 | For delivery &1 &2 LDC merge done |
| 105 | Specific material updated in LDC |
| 106 | Ticket processing stopped at LDC event; cannot re-execute from here |
| 107 | Delivery not found |
| 108 | Delivery document &1 created |
| 109 | Call-off process from OF ended |
| 110 | Delivery &1 created for the STO &2 |
| 111 | Operation for determining marketing material failed for material &1 |
| 112 | Material determination skipped for marketing materials |
| 113 | OF determination failed |
| 114 | Cannot determine material |
| 115 | Cannot find data for nomination key &1 |
| 116 | Cannot find reference document |
| 117 | Material doc. GR &1 created |
| 118 | Cannot convert quantity as &1 |
| 119 | Nom. Confirmation Ticket &1 is in error state; cannot process further |
| 120 | No preceding documents found for nomination &1 item &2 |
| 121 | Order type for Incoterms &1 and contract type &2 not maintained |
| 122 | Unassigned scenario in 3rd party purchase TTO or Return is not allowed |
| 123 | IBD does not exist |
| 124 | OBD does not exist |
| 125 | IBD &1 exists for STO |
| 126 | No data found for ticket key &1 |
| 127 | Error in LDC event status update of "OF Determination Triggered" |
| 128 | LDC event status updated to "OF determination triggered" |
| 129 | Error in LDC event status update of "OF execution failed" |
| 130 | LDC event status updated to "OF execution failed" |
| 131 | Error in LDC event status update of "OF execution successful" |
| 132 | LDC event status updated to "OF execution successful" |
| 133 | LDC event status updated to "OF determination successful" |
| 134 | Application document &1 created |
| 135 | Data not found for the delivery |
| 136 | Material document not found |
| 137 | Title transfer determined is neither Destination nor In Transit |
| 138 | Application document updated |
| 139 | Error in LDC event status updated to "OF determination successful" |
| 140 | Document type is not Return Sale Type(H) |
| 141 | Reference document mandatory for returns processing |
| 142 | Purchase order and delivery are not linked |
| 143 | Orchestration Framework has been called |
| 144 | Vendor is not a return type |
| 145 | PO line item is not flagged for return |
| 146 | ************************************************************************ |
| 147 | Orchestration Framework processing has been completed |
| 148 | STO &1 &2 and Outbound Delivery &3 &4 are not linked |
| 149 | STO &1 &2 is not called-off against contract &3 &4 |
| 150 | STO is not called-off against any contract & & & & |
| 151 | Called-off contract found for the STO &1 &2 |
| 152 | No called-off contract found for STO &1 &2 |
| 153 | STO &1 &2 has enough open quantity |
| 154 | STO &1 &2 does not have enough quantity |
| 155 | Load event needs to be successfully executed first for LDC ID &1 |
| 156 | No LDC ID found for ticket key &1 |
| 157 | Delivery && has been already PGI'd |
| 158 | Origin acceptance flag should be checked for order item |
| 159 | Origin acceptance flag should not be checked for order item |
| 160 | Order item should be POD relevant |
| 161 | Delivery &1 updated with the storage location and quantity |
| 162 | Update of delivery &1 failed |
| 163 | Merge needs to be done for load LDC ID &1 |
| 164 | Load needs to be executed first for Unload LDC ID &1 |
| 165 | Transaction reloaded after ticket re-execution |
| 166 | 109 posting is already done for delivery &1 |
| 167 | No document posting shall be carried out for this scenario |
| 168 | Delivery cannot be created as number of carlots has been consumed |
| 169 | Ticket &1 cannot be re-executed until ticket &2 is processed |
| 170 | No data found for ticket key &1 |
| 171 | No data found for delivery &1 |
| 172 | LDC IDs should be released for other items also for delivery &1 |
| 173 | Puchase org not found for plant; moved to Unassigned Scenario &1 &2 |
| 174 | Title transfer destination considered for contract determination &1 &2 |
| 175 | Unplanned inter/intra scenario is not supported |
| 176 | Unplanned third party sales is not a valid scenario |
| 177 | For third party purchase TTD, execute unload |
| 178 | Nomination & & currently locked |
| 179 | Auto application has been triggered |
| 180 | Auto application could not be triggered |
| 181 | Divide by zero error occured |
| 182 | You have no authorization to view this transaction |
| 183 | For application instruction &1, no postings will happen during Load |
| 184 | Error occurred while changing the delivery with batch split. |
| 185 | Function module for POD reversal triggered |
| 186 | Evaluating automatic storage agreement rule for &1 in &2 |
| 187 | Outbound delivery not found |
| 188 | Re-execution not authorized |
| 189 | Ticket &1 with corrupt status cannot be processed |
| 190 | No LTC exists for order &1 |
| 191 | Error during application diversion process |
| 192 | Application diversion process was successful |
| 193 | Application document does not exist |
| 194 | Assignment/Call-off queue has failed for order &1 |
| 195 | Not able to find Deliveries created for PO |
| 196 | Not able to determine SD document category |
| 197 | DB Commit Failed |
| 198 | Cannot Read Base UOM for Material &1 |
| 199 | Document to be created manually from LDC Brazil tab |
| 200 | BR: Good Receipt Mode determined Automatic |
| 201 | Either sales order call-off does not exist or assignment queue failed. |
| 202 | LDC ID information missing |
| 203 | Orchestration engine reversal triggered |
| 204 | Forward documents not found. FM for &1 deletion/reversal skipped |
| 205 | LTC &1 item &2 missing for document &3 item &4 in WBHD |
| 206 | Function module for inbound delivery deletion triggered |
| 207 | Delivery document &1 deleted from UIS events |
| 208 | Function module for goods movement reversal triggered |
| 209 | Function module for third party deletion triggered |
| 210 | Function module for purchase order deletion triggered |
| 211 | Function module for purchase order deletion skipped |
| 212 | Unknown goods movement reversal document type &1 |
| 213 | Purchase order &1 deleted |
| 214 | Ticket not created. LDC not found. |
| 215 | Ticket reversal posting failed |
| 216 | Error occured while updating LDC event status &1 |
| 217 | LDC event status updated to &1 |
| 218 | Database save failed |
| 219 | Could not read plant from TSW location &1 |
| 220 | Storage agreement (&1/&2) determined from BRFplus rule |
| 221 | Assignment to storage agreement (&1/&2) started |
| 222 | Storage agreement (&1/&2) is valid |
| 223 | End of storage agreement assignment |
| 224 | Function module for outbound delivery deletion triggered |
| 225 | Material &1 is storage relevant. Scenario will go unassigned. |
| 226 | Call-off skipped. No contract refernce exists. |
| 227 | Function module for sales order rejection triggered |
| 228 | Function module for sales order rejection skipped |
| 229 | Sales order &1 rejected |
| 230 | Order &1/&2 updated in ticket document flow |
| 231 | Call-off exists for sales order &1. Cannot reverse sales order. |
| 232 | Function module for sales order update triggered |
| 233 | Default storage agreement not found for LDC |
| 234 | Application document is unassigned |
| 235 | BRFplus rule has errors |
| 236 | Automatic storage agreement found for &1 and &2 |
| 237 | Automatic storage agreement not defined |
| 238 | Goods movement data is not consistent. |
| 239 | Call-off skipped. No contract reference exists. |
| 240 | Reading process for ticket execution failed |
| 241 | Could not read reference trading contract. |
| 242 | Vendor entered in LDC is not in reference trading contract. |
| 243 | Customer entered in LDC is not in reference trading contract. |
| 244 | Could not read LDC data. |
| 245 | Could not read Application Document data. |
| 246 | LDC quatity &1 &2 determined. |
| 247 | Call off Quantity &1 &2 determined. |
| 248 | Application document type &1 creation triggered |
| 249 | Error during posting adjustments. |
| 250 | LDC &1 is Automatic Application Processing Options |
| 251 | Incoterm &1 defined |
| 252 | LDC quantity is greater than the Purchase order &1 &2 qty. |
| 253 | &1 creation skipped. |
| 254 | Order type for application instruction &1 is not maintained in BRF+ |
| 255 | In online mode, GTM implementation should be inactive |
| 256 | In queue mode, GTM implementation should be active |
| 257 | LTC creation mode &1 |
| 261 | Function module for SIT adjustment triggered |
| 266 | SIT adjustment completed |
| 267 | Load quantity determined &1 &2 |
| 268 | Unload quantity determined &1 &2 for line item &3 |
| 271 | No SIT adjustment triggered for line item &1 |
| 273 | Movement type not determined |
| 279 | Function module for goods movement reversal skipped |
| 280 | Error in post dcm badi for application documents. |
| 307 | You can select only one incoterm to be the standard. |
| 308 | You can only set a destination incoterm to be the standard. |
| 309 | Ticket &1 cannot be executed again as a new version of the ticket exists |
| 310 | Delivery &1 is not POD relevant |
| 311 | POD cancellation goods movement number could not be identified |
| 312 | POD cancelled |
| 313 | POD cancellation goods movement &1 posted |
| 314 | Purchase order &1 changed successfully |
| 315 | Unload plant &1 determined for delivery &2 line item &3 |
| 316 | Load plant &1 determined for material document &2 line item &3 |
| 317 | Goods Movement &1 reversed with document &2 for plant SIT adjustment |
| 318 | Inbound Delivery &1 deleted for plant SIT adjustment |
| 320 | Material &1 on trading contract is different from material &2 on LDC. |
| 321 | Material &1 on purchasing document is different from material &2 on LDC. |
| 322 | Material &1 on sales order is different from material &2 on LDC. |
| 323 | Material &1 on storage agreement is different from material &2 on LDC. |
| 324 | Material &1 on nomination is different from material &2 on LDC. |
| 325 | Execution of junction function is failed for unload event. |
| 326 | LDC &1 event &2 cannot be saved with 0 gross quantity, add new weight |
| 327 | Reversal of staging goods movement failed |
| 328 | Reversal staging document &1 created |
| 329 | Staging reversal successful |
| 330 | Nomination &1 has been created successfully |
| 331 | No contract found for this LDC |
| 332 | Sales order &1 created without contract reference |
| 333 | Pegging ID &1 generated |
| 334 | Called-off contract &1 item &2 quantity &3 &4 |
| 335 | No contract was determined |
| 336 | Call-off skipped, not enough quantity on the contract |
| 337 | Tolerance was applied on contract &1 item &2 |
| 338 | Pricing lot &1 of contract &2 item &3 |
| 339 | No. of records found with base search criteria &1 |
| 340 | Sequence of contract pricing lots to be applied |
| 341 | Seq &1 contract &2/&3 pricing lot &4 |
| 342 | No. of records found with optionality search criteria &1 |
| 343 | No. of records found with physical commodity search criteria &1 |
| 344 | For seq &1 contract &2/&3, no pricing lot exists &4 |
| 345 | AAD not created, LDC vendor &1 is not linked to AP16 goods supplier |
| 346 | MAD not created, LDC vendor &1 is not linked to AP16 goods supplier |
| 347 | No. of records found with search w/o MOT criteria - &1 |
| 348 | exceptions of HANA DB objects |
| 349 | Contract determination switch is off |
| 350 | &1 is not a valid specific material for material &2 |
| 351 | BRF Rule 'AP32' for Unplanned Purchase/Sales Contract sequence called |
| 352 | Contract &1 added with Sequence &2 Prepayment type &3 Category &4 |
| 353 | Applicaton failed to apply to Contract.Check application log for details |
| 354 | Application processed in &1 mode. |
| 355 | Pricing distribution failed. Please check the pricing log |