/ACCGO/BR_UIS -
The following messages are stored in message class /ACCGO/BR_UIS: .
It is part of development package /ACCGO/BR_UIS in software component LO-AGR-LOC-BR. This development package consists of objects that can be grouped under "ACCGO: Brazil Load Data Capture".
It is part of development package /ACCGO/BR_UIS in software component LO-AGR-LOC-BR. This development package consists of objects that can be grouped under "ACCGO: Brazil Load Data Capture".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Enter NF number |
| 002 | Split scenario is only available for a natural person |
| 003 | Triangular operation is not available for a natural person |
| 004 | Enter total value of nota fiscal for certifcate category NF |
| 005 | Enter a delivery note number |
| 006 | Certificate category should be nota fiscal |
| 007 | Brazil: company is not authorized to split scenario to LDC |
| 008 | Enter a base amount |
| 009 | Enter total weight and base unit of nota fiscal in the Brazil tab |
| 010 | Cannot save; unload event must be released |
| 011 | For natural person purchase scenario weights and grades must be final |
| 012 | Error during final application |
| 013 | Overfill error |
| 014 | Check DPQS details; error in evaluation |
| 015 | Enter a reference contract number and item |
| 016 | Enter a purchase order number and item |
| 017 | Vendor data does not exist |
| 018 | Customer data does not exist |
| 019 | Enter a valid document number and year |
| 020 | Trading contract is not a purchase contract |
| 021 | PO &1 cannot be assigned to a contract |
| 022 | Tax code &1 is not valid |
| 023 | NF valid must be marked and NF values must be informed for this scenario |
| 024 | No NF expected for natural person |
| 025 | This LDC split is valid |
| 026 | Internal LDC split error |
| 027 | Split weight do not match LDC unload weight |
| 028 | Split NF weight and unit of measure are mandatory |
| 029 | Reference load LDC &1 does not exist |
| 030 | Reference load LDC &1 already contains an unload event |
| 031 | Split quantity is mandatory |
| 032 | Vendor is mandatory |
| 033 | Vendor does not exist |
| 034 | Split validation error |
| 035 | Fill analysis details for parent split |
| 036 | Nota fiscal was not found on &1 scenario; provide a nota fiscal number |
| 037 | Invoice &1 with NF &2, does not belong to purchase order &3/&4 |
| 038 | Nota fiscal &1 does not belong to any invoice document from vendor &2 |
| 039 | Unplanned purchase order cannot be used in natural person scenario |
| 040 | Please provide a unit of measure for the delivery nota fiscal weight |
| 041 | The LDC quantity is greater than the available invoice quantity |
| 042 | Split application instruction is not allowed for child split |
| 043 | Material &1 is different from reference contract material &2 |
| 044 | Vendor &1 is different from reference contract vendor &2 |
| 045 | Nota fiscal was set as 'Final'; a new LDC is not possible |
| 046 | Enter vendor number |
| 047 | Enter royalties agreement with the vendor |
| 048 | Split &1: Generated split event (LDC &2) is not obsolete |
| 049 | Material &1 is different from PO item material &2 |
| 050 | Vendor &1 is different from PO vendor &2 |
| 051 | Please provide a purchasing document |
| 052 | Purchasing document &1 does not exist |
| 053 | Item &1 was not found in purchasing document &2 |
| 054 | Enter unload event weight details |
| 055 | Enter load event weight details |
| 056 | Enter load event analysis details |
| 057 | Contract &1 does not exist |
| 058 | Item &1 was not found in contract &2 |
| 059 | Enter unload event analysis details |
| 060 | Analysis detail is missing for required characteristics |
| 061 | Error while reading DPQS header data |
| 062 | For natural person scenario, enter unload event details |
| 063 | Logistically adjusted quantity (LAQ) is less than or equal to zero |
| 064 | Enter total value of delivery nota fiscal for certificate category NF |
| 065 | Enter total weight and base unit of delivery nota fiscal in Brazil tab |
| 066 | UoM &1 is not allowed for material &2 in delivery nota fiscal |
| 067 | Movement type not found movement type customizing |
| 068 | Error in ticket reading while calling goods receipt |
| 069 | Inbound delivery was not found in document flow. Goods receipt not exec. |
| 070 | Qty in unit of entry should match to LDC quantity, that is, &1 |
| 071 | Unit of entry should match to LDC unit, that is, &1 |
| 072 | Delivery note number should be &1 |
| 073 | Qty in deliv. note should match LDC deliv. note qty, that is, &1 |
| 074 | Deliv. note qty UoM should match LDC deliv. note qty LDC, that is, &1 |
| 075 | Storage location should match LDC, that is, &1 |
| 076 | Delivery note number should match LDC, that is, &1 |
| 077 | The movement type should be &1 |
| 078 | Header text should match LDC invoice nota fiscal number, that is, &1 |
| 079 | Tax code should match LDC, that is, &1 |
| 080 | Alternative base amount should match LDC, that is, &1 |
| 081 | Soft assignment check fails for the input LDC quantity |
| 082 | Delivery note fiscal tax code in Brazil tab is empty |
| 083 | Delivery note fiscal alternativa base amount in Brazil tab is empty |
| 084 | Goods receipt not found |
| 085 | More than one invoice found; please provide NF number in Brazil tab |
| 086 | Invoice was not found for purchase order &1; &2 is not possible |
| 087 | Application instruction 81 is only used by locations in Brazil |
| 088 | Ref. docs for Brazil commingled scenario shall be entered in Brazil tab |
| 089 | Logistically adjusted quantity (LAQ) could not be calculated |
| 090 | Contract &1 is not approved |
| 091 | Vendor &1 is different from the one informed at split, &2 |
| 092 | Delivery note quantity is larger than contract &1/&2 available quantity |
| 093 | Appl. instr 81 (Brazil commingled) can be used only for incoming loads |
| 094 | Cannot create load event for parent split |
| 095 | Return is not permitted for PO items with GR-based IV |
| 096 | LAQ must be higher than zero. Check DPQS for material &1, TSW location &2 |
| 097 | To release load event kindly create unload event also for this scenario. |