OE - IS-Oil: ITA/TPI messages
The following messages are stored in message class OE: IS-Oil: ITA/TPI messages.
It is part of development package OIK in software component IS-OIL-DS-TAS. This development package consists of objects that can be grouped under "TAS/TPI Common Objects".
It is part of development package OIK in software component IS-OIL-DS-TAS. This development package consists of objects that can be grouped under "TAS/TPI Common Objects".
Message Nr ▲ | Message Text |
|---|---|
| 000 | IS-Oil / TAS: Create SD/MM Calloff, Delivery, Goods issue (000-099) |
| 001 | Sales contract & does not exist |
| 002 | Delivery note & does not exist |
| 003 | Delivery note & does not have an item |
| 004 | Delivery note & has more than one item. TAS allows only one item |
| 005 | Purchase Calloff for delivery note & could not be created |
| 006 | Purchase Calloff item & & does not exist |
| 007 | Sales calloff was not created |
| 008 | Delivery note for sales calloff & was not created |
| 009 | Function OIK_LID_REFERENCE_GET abended: & |
| 010 | Function & does not exist |
| 011 | Function & is not active |
| 012 | Function OIK_LID_FUNCTIONS_GET abended: & |
| 013 | All functions for this IDOC succesfully processed |
| 014 | Idoc data changed |
| 015 | This Matchcode cannot be used by Transaction & |
| 016 | Material & cannot substitute material & |
| 017 | Unit of measure & is not an SAP unit of measure (is not in table 006) |
| 018 | Ship-to party & not maintained in contract & |
| 019 | Plant, storage location or shipping point is missing in E1OILT1 |
| 020 | Purchase order no or item no is missing in E1OILT1 |
| 021 | Function & does not process documents of type & |
| 022 | DB error during creation of LID Document Data Table OIK01 |
| 023 | Error in Function OIK_CHANGEPTR_OILORD_CREATE (create change pointer) |
| 024 | Material temperatur and/or material temperatur unit is missing |
| 025 | Loading date in future (&) is not allowed |
| 026 | Batch and valuation type together are not allowed in E1OILT1 |
| 027 | Shipping point & not allowed for plant & Storage location & |
| 028 | Items deleted from CVBAP in VBAP_KOPIEREN_PRUEFEN(FV45CF0V) |
| 029 | Error in exchange assignment. |
| 030 | & Idoc(s) with load information forwarded |
| 031 | Field &: '&' / First byte is not a valid character |
| 032 | Field &: '&' / Invalid character in field |
| 033 | Field &: '&' / Multiple decimal point is not allowed |
| 034 | Field &: '&' / Field is not fullfilled by spaces |
| 035 | Field &: '&' / Decimal point is not allowed |
| 036 | Field &: '&' / Minus sign is not allowed |
| 037 | Field &: Reserve |
| 038 | field &: Reserve |
| 039 | Field &: '&' / Unknown error |
| 040 | Error in function OIK_SD_DELIVERY_CREATE (&) _ |
| 041 | Error in function OIK_EXTERNAL_ASTM_DATA_GET |
| 042 | Program abended because of abnormal situation |
| 043 | Calloff & and delivery & have been saved. |
| 044 | Neither a calloff nor a delivery has been saved. |
| 045 | Calloff & has been saved. |
| 046 | Item & & is completely processed. |
| 047 | Undefined error during creation of purchase calloff (ROIALB02). |
| 048 | This delivery was created by the TAS Interface and can only be displayed |
| 049 | The number of calloff items differ from the number of load items |
| 050 | The number of delivery items differ from the number of calloff items |
| 051 | There are no deliveries selected |
| 052 | Function &1 not successfully carried out for IDoc &2 |
| 053 | Shipment type & not defined for auto del conf at & |
| 054 | UoM conversion from ISO to SAP not possible for & & |
| 055 | Material conversion from EAN to SAP not possible for & |
| 056 | Shipment number missing |
| 057 | Changes to BAPI data not allowed for shipment type & at & |
| 058 | Changes to BAPI data not allowed for DCP in status & |
| 059 | DCP data & & currently locked |
| 060 | Update of delivery confirmation table not possible for & & |
| 061 | Trigger of BP Event & not possible for & & |
| 062 | Shipment & not yet scheduled |
| 063 | Shipment & closed > no more changes possible |
| 064 | Shipment & not loaded -> del. confirmation not possible |
| 065 | Shipment & nothing to do |
| 066 | Sales order & + delivery & created |
| 067 | Shipment & not completely confirmed |
| 068 | Previous shipment number is missing |
| 069 | No function group defined for delivery confirmation process |
| 070 | More than one function group defined for delivery confirmation process |
| 071 | No function group defined for TPI interface |
| 072 | More than one function group defined for TPI interface |
| 073 | Enhancement OIKSTRS1 must be migrated to OIKSTRS2 -> see long text |
| 074 | The TPI relevancy has been moved to a new tool --> see long text |
| 080 | Create delivery for order that has been passed to external TPI system? |
| 081 | Create delivery due list for order that has been passed to TPI system? |
| 082 | Assign delivery for TPI-relevant orders to TD shipments? |
| 083 | Change shipment that has been created by the external TPI system? |
| 092 | Function 'OIK_CUSTOMER_FUNCTION_EXAMPLE' not successfully carried out |
| 093 | Function 'OIK CUSTOMER FUNCTION EXAMPLE' successful |
| 100 | |
| 101 | No driver IDoc created. No data selected. |
| 102 | No rack meter IDoc created. No data selected. |
| 103 | No compartment meter IDoc created. No data selected. |
| 104 | No transport unit IDoc created. No data selected. |
| 105 | No vehicle IDoc created. No data selected. |
| 106 | No IDoc created. No data selected. |
| 150 | Shipment number & does not exist. |
| 151 | Shipment & is already delivery confirmed. Process not possible. |
| 152 | No vehicle exists in shipment & in status 4 or 5. |
| 153 | Prior-to-load changes are allowed only for scheduled shipments |
| 200 | IS-OIL/TAS Data Maintenance (200-299) |
| 201 | Item not TAS relevant |
| 202 | Load-Id deactivated |
| 203 | Load-Id deleted |
| 204 | Load-Id already exists |
| 205 | Load-Id copied from Master-Data |
| 206 | Choose an entry |
| 207 | No TAS-Data maintained for item & |
| 208 | Data copied from Master-Data |
| 209 | Load ID does not exist; check the master data |
| 210 | Validity period overlaps existing period in TAS Reference table |
| 211 | Item not TAS relevant - Data will be displayed |
| 212 | Copy-Flag active - Data will be displayed |
| 213 | The entered item &/& is not a purchase order or a purchase contract item |
| 214 | Purchase item & & is not exchange-related |
| 215 | Please enter MM-Document number |
| 216 | End of validity period must be 'greater or equal to' (later than) start |
| 217 | Validity period has to be within the contract start and end dates |
| 218 | No history data available |
| 219 | Invalid date & |
| 220 | Invalid time & |
| 221 | No valid Load-Id of LID type & found |
| 222 | Error during INSERT & & & |
| 223 | Error during UPDATE & & & |
| 224 | Error during DELETE & & & |
| 225 | LID & - & is currently locked by user & |
| 226 | System error during locking procedure |
| 227 | Error during locking procedure |
| 228 | Already editing new record |
| 229 | Validity period changed! Please check Load IDs |
| 230 | Invalid adjustment of validation period! Please correct Load IDs. |
| 231 | Please maintain contract start/end date for Load-Id assignment |
| 232 | Valid Load IDs of type & exist but marked for deletion/blocking |
| 240 | Field & is not valid for TAS Relevance Pickup |
| 241 | Please maintain ranking for field & |
| 242 | Field & is not valid for TAS Relevance Shipment |
| 250 | Shipment &: Receiving plant & not scheduled |
| 251 | Shipment &: Document/Plant not unique |
| 252 | Shipment &: Document not found |
| 253 | Shipment &: Document type not supported |
| 300 | LID-type &1 already used. Please specify a unique LID-type |
| 301 | Control structure &1 already used! Please specify a unique Control Struc |
| 302 | LID-Type &1 entered twice! Enter a new LID Type. |
| 303 | Control Structure &1 entered twice ! Please enter a new Control Structure |
| 304 | No Entry for field &1! Please enter a value! |
| 305 | Entry &1 is not valid for field &2! Please use PF4 for help! |
| 306 | Lid-Type &1 not valid &2! Please use PF4 for help! |
| 307 | LID NO &1 is not active and can't be used! |
| 308 | SeqNo &1 already used for Function Group &2! Please choose a new Number. |
| 309 | Seq-No &1 entered twice in editor mode! Choose a different one! |
| 310 | Subsequent document type &1 is not valid for document category &2 |
| 311 | For document category &1 no subsequent document type is available |
| 312 | The document type & is not valid for orders! |
| 313 | Enter a value for number range number! Field is mandatory! |
| 314 | Number range number &1 does not exist for object OIK_LID! |
| 400 | IS-Oil / TAS: Reports (400-499) |
| 416 | Please position cursor into a valid line in the list. |
| 417 | Place Cursor on a LID-Number, SD-DocNo or IdocNo to show their details. |
| 418 | No data found for LID & in tables OIKLID and OIKLIDW |
| 419 | Please position cursor on a valid SD-DocNo. |
| 420 | Please position cursor on a valid LID-Number. |
| 421 | Internal Error: List No &1 |
| 422 | Int.Error: No equiv. entry to OIK02B in OIK01 SD-DocNo &, LIDNO & |
| 423 | Int.Error: No entry in VBAP for KDAUF &,ITEM & |
| 424 | Int.Err: More than 1 entry in VBAP for KDAUF &, ERDAT & |
| 425 | Int.Err: No entry in LIPS for Delivery &, Item & |
| 426 | Int.Err: More than 1 entry in LIPS for LIEFN &, ERDAT & |
| 427 | Int.Error: more than 1 entry in OIK01 for SD-DocNo &, LIDNO & |
| 428 | Int.Err: No entry in table OIKLRT for Spras &, Reatype &, Reacode & |
| 429 | Place Cursor on a LID-Number or SD-DocNo to display details |
| 440 | Could not find data for SD-DocNo & in VBAK or LIKP |
| 441 | Please position the cursor on a field that is not empty |
| 442 | Place Cursor on a valid LID |
| 443 | Place Cursor on a valid SD-DocNo |
| 444 | Place Cursor on a valid Idoc-Number |
| 450 | Number of Documents per Job recalculated ! |
| 451 | &: IDOC: & - LID: & - MSG: & |
| 452 | & IDOCs selected |
| 453 | Recieve RFC failed: & & & & |
| 454 | Get Tasklist error: & & & & |
| 455 | Set Tasklist error: & & & & |
| 456 | Parallel processing canceled ( & RFCs failed = & % ) |
| 457 | Goods issue: & & & & |
| 458 | Reset Tasklist: & - IDOC: & - LID: & - MSG: & |
| 459 | & & & & |
| 508 | No selection group activated |
| 509 | Transportation Planning Point & not assigned to external planning system |
| 510 | There are no Transport Planning Points with external planning systems |
| 511 | Transportation Planning Point & is not defined |
| 512 | No receiving system defined |
| 515 | No receiving system defined |
| 516 | Compartments cannot be copied to new vehicle &1 |
| 517 | Compartments do not exist |
| 518 | Vehicle &1 has not been scheduled |
| 519 | No load-relevant data found for the shipment &1 |
| 520 | No ext. planning systems have been maintained for trans. planning points |
| 521 | Specification SELECTION_SET and SELECT_OPTIONS are alternatives |
| 522 | Set checkbox |
| 550 | Changing Hierarchy causes the Relevance to be updated automatically. |
| 555 | ARRAY op error: DB table=&, op=&, rc=&, lines=& |
| 556 | SAVE op error: & unknown entries on & posting table, key= & & |
| 559 | Inconsistency in program &, global doc no = &, local doc no = & |
| 600 | & location descriptions sent to the transportation planning system |
| 606 | The OIL-TPI subsystem has been de-activated in this client |
| 607 | The OIL-TPI subsystem has been activated in this client |
| 609 | Table group authorization OIK is missing for this transaction |
| 610 | Order & is currently blocked by another user |
| 611 | Order & already transmitted to planning system & |
| 612 | No data determined for the selection. |
| 613 | & output records created. & could not be created. |
| 614 | No orders found for the selection specified |
| 615 | No message type combined with IDoc |
| 616 | No message type chosen for IDoc processing! |
| 617 | No TPI relevant item for order &. |
| 620 | IDoc category & is not defined for communication with logical system & |
| 630 | The selection log is empty |
| 640 | &1 is an invalid date (choose a date between &2 and &3) |
| 641 | All subsequent lines after date &1 will be lost |
| 642 | Choosen times for date & are overlapping other times of the time table |
| 643 | The date &1 is more than one year behind the date &2 |
| 644 | All lines with dates earlier than &1 will be lost |
| 645 | &1: No congruence concerning master data (&2 - &3) |
| 646 | &1: 'time from' and 'time to' can't be the same |
| 647 | &1: No overlap between time frame and master data (&2 - &3) |
| 649 | &1: Time frame data do not match the customer master data |
| 650 | Order & cannot be sent to TPS. It has exceeded the credit limit. |
| 651 | From Date must be earlier than To Date |
| 652 | From Time must be earlier than To Time |
| 700 | Vehicle & is not assigned to driver & |
| 701 | Consider the subsequent delivery documents (Refresh) |
| 702 | Deletion failed! Please refresh list! |
| 703 | Log entry(-ies) deleted! |
| 704 | No table entries found for specified key |
| 705 | Delivery & already planned by foreign user - Replanning Shipment ... |
| 706 | Place cursor on a valid entry of the log table |
| 707 | No log table entry selected |
| 708 | Place cursor on a valid item line |
| 710 | Delivery & has different Load Plants (selection from first item) |
| 711 | Vehicle has to be maintained for shipments to be created |
| 712 | Collecting data ended with Warnings. Shipment->Check->Display Warnings |
| 713 | Drv./Veh.-Assignm. not maintained for Driver &1 at &2 Shift &3. |
| 714 | Check ended with Warnings. Shipment->Check->Display Warnings |
| 715 | Shipment & has already been & |
| 716 | Shipment & does not exist |
| 717 | Please enter document sequence number |
| 718 | Duplicate entries for document sequence within a trip |
| 719 | Please enter trip sequence number |
| 720 | Delivery & has already been assigned |
| 721 | Delivery & does not exist |
| 722 | Delivery & has already been & |
| 723 | Document & does not exist |
| 724 | Please choose Shipment from planning screen |
| 725 | Object Shipment & is in use by user & |
| 726 | System error during locking shipment & |
| 727 | Error during locking shipment & |
| 728 | Document & is assigned to shipment &. Generation will change assignment. |
| 729 | Duplicate entries for Trip sequence number |
| 730 | Trip number required for Shipments to be created |
| 731 | Vehicle & in Shipment & don't match the maintained Vehicle assignment |
| 732 | Nothing to generate |
| 733 | Shipment & has been deleted. Shipment will be removed from Planning |
| 734 | Shipment & has already been & |
| 735 | Vehicle & has already been assigned |
| 736 | The Vehicle assignment data for driver & was saved |
| 737 | The data was already saved |
| 738 | Driver &1 and Vehicle &2 do not match the location |
| 739 | Check performed successfully |
| 740 | Data is currently locked by user &. Display only |
| 741 | System error during locking procedure |
| 742 | Error during locking procedure |
| 743 | Enter planned start date for shipment |
| 744 | Shipment type does not exist |
| 745 | Only Shipments with matching Transp.Plann.Point & can be included |
| 746 | Include failed. Shipment &1 is already in Trip Planning |
| 747 | Generation executed successfully |
| 748 | Generation executed with warnings |
| 749 | Delivery & & & |
| 750 | Ranking of TAS Relevance fields not maintained |
| 751 | View is not designed for field & |
| 752 | Assignment for driver &, vehicle &, shift & and date & read from database |
| 753 | Assignment for vehicle & not possible. Wrong transport. planning point. |
| 754 | Driver vehicle assignment saved for transportation planning point &. |
| 755 | Vehicle & already assigned to driver & in same shift on same day. |
| 756 | Error during locking of driver vehicle assignment |
| 757 | No vehicle within specified range & to & for transp. planning point &. |
| 758 | Assignment for driver &, vehicle &, shift & and date & read from database |
| 759 | Duplicate key for vehicle & driver & loaddate & shift &. |
| 760 | Select at least one Shipment stage |
| 801 | |
| 806 | Manual changes to ETA are not allowed as user exit OIKSHPPL is active |
| 807 | & location descriptions sent to the Transportation Planning System |
| 808 | No entry for message type & in edimsg found. No IDocs will be created. |
| 809 | No parallel use of application objects allowed |
| 843 | &1 entries of &2 selected entries have been deleted |
| 844 | Shipment & and the underlying documents have been re-created |
| 845 | Simultaneous use of swap deliveries and delivery item maintenance |
| 846 | Sales order & created |
| 847 | Internal order & exists in SAP system |
| 848 | Document & unplanned from shipment & via IDoc &. |
| 849 | Referencing is not unique within the same qualifier |
| 850 | Messages for inbound shipment processing |
| 851 | Missing E1OILSQ segment for order & position &. |
| 852 | Shipment deletion is not possible, since no the creation was no success |
| 853 | Shipment & was already deleted via another IDoc |
| 854 | Shipment & deleted via IDoc & |
| 855 | Delivery & was already deleted via another position or IDoc |
| 856 | Delivery & deleted using IDoc & |
| 857 | No apropriate delivery for item & position & on shipment & (external no). |
| 858 | No apropriate order for item & position & on shipment & (external no's). |
| 859 | Order & deleted via IDoc & |
| 860 | Order & was already deleted via another position or IDoc. |
| 861 | No shipment was created for the external number &! |
| 862 | No entry within OIK29 with the right status for doc. & position &! |
| 863 | Shipment with external no. &: Change not possible, error with items! |
| 864 | No E1OILSI segment found for E1OILSP segment. Item no. & position no. & |
| 865 | Allocation of document & on shipment &, changed via IDoc & |
| 866 | Document & planned onto Shipment & via IDoc &. |
| 867 | Document & created via IDoc &. |
| 868 | Document & not planned onto a shipment (via IDoc &). |
| 869 | Document & unplanned via IDoc &. |
| 870 | Old deliveries deleted |
| 871 | No deletion of old deliv. for order & pos &. Missing related pos. in IDoc |
| 872 | No change of order for order & pos &. Delivery exists. |
| 873 | No change of order for order & pos &. Other docs than delivery exist. |
| 874 | No change of order for order & pos &. Internal Delivery exists. |
| 875 | Unknown change sign for order & position &. |
| 876 | Reference to non-existing order. External order & posnr &. |
| 877 | Wrong plant without change sign on incoming order & posnr &. |
| 878 | delivery recreated via IDoc &. New delivery no. & old no &. |
| 879 | Related order & position & changed by incoming IDoc & |
| 880 | Storage object assignment could not be saved for doc & on IDoc &! |
| 881 | Processing not possible. Missing data entry. |
| 882 | Specify only order or delivery. |
| 883 | Position on different deliveries. |
| 884 | No sold-to maintained for order & ship-to &. |
| 885 | Unit of measure conversion not possible for order & unit & Reason & |
| 886 | Too many sold-to's maintained for order & ship-to &. |
| 887 | Processing of Shipment abandonned by user & at &. |
| 888 | Automatic determination of Storage loc. not possible, multiple options. |
| 889 | Material not available at plant & storage location &. |
| 890 | Plant is not changed. No processing necessity. |
| 891 | Missing unit of measure for documenet with external no. & position & |
| 892 | Shipment type could not be determined for shipment & on IDoc &! |
| 893 | Internal update to segment numbering failed for shipment & on IDoc &! |
| 894 | Shipment & not created. Previous documents ended with errors. |
| 895 | IDoc processing failed. Check TPI flow log for error details. |
| 896 | Delivery & deleted. Substitute delivery & created. |
| 897 | Material &1 in Document &2 item &3 different from loaded material &4. |
| 898 | Select the shipment that you want to display |
| 899 | Deletion of the document & failed. |
| 990 | Ranking of TAS Relevance fields not maintained |