FINLOC_JP_INVSUM - Japan Invoice Summary Extension
The following messages are stored in message class FINLOC_JP_INVSUM: Japan Invoice Summary Extension.
It is part of development package GLO_FIN_BP_IS_JP in software component FI-LOC-FI-JP. This development package consists of objects that can be grouped under "Business Partner extensions for Financials - JP Inv Summary".
It is part of development package GLO_FIN_BP_IS_JP in software component FI-LOC-FI-JP. This development package consists of objects that can be grouped under "Business Partner extensions for Financials - JP Inv Summary".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Enter 'Payer' for recipients for & company code |
| 002 | Enter 'Recipient' for customers for & company code |
| 003 | Enter PID for & company code |
| 004 | Entered payer (&) does not have role 'Payer' for & company code |
| 005 | Entered recipient (&) does not role 'Recipient' for & company code |
| 006 | Customer is still used as a payer [for ex., by (&)] for & company code |
| 007 | Role can only be changed to 'Recipient' for & company code |
| 008 | Customer is still used as a recipient [for ex., by (&)] for & cmpny code |
| 009 | Action cancelled; check your entries |
| 010 | Check errors occured. Saving is not possible. |
| 011 | Monthly invoices without payer invoices exist for recipient & for & c.c |
| 012 | Invoice Summary line items exist for recipient & and payer & |
| 013 | Confirmation of incoming payment has to be created manually |
| 014 | There are input errors in table 'payment terms' for & company code |
| 015 | Enter 'Valid from' date |
| 016 | Table 'payment terms' contains lines with same keys |
| 017 | Enter valid payment term |
| 018 | Table 'nayose' contains lines with same keys |
| 019 | Enter valid sequence number for & company code |
| 020 | Enter valid sequence number |
| 021 | Enter alternative name for payer for & company code |
| 022 | Enter 'Valid from' date for & company code |
| 023 | Enter valid payment term for & company code |
| 024 | Company Code & and customer & have more than one record |
| 025 | When ISJP role is empty, redundant hierarchy data also need to be empty |
| 026 | Except for the current role data, all other data should be cleared |
| 027 | Entered customer & does not match the being processed customer & |