FSBP_FND_INBOUND -
The following messages are stored in message class FSBP_FND_INBOUND: .
It is part of development package FS_BP_FND2_ESA_INBOUND in software component FS-BP. This development package consists of objects that can be grouped under "Inbound Service Proxies for FS-BP in FND".
It is part of development package FS_BP_FND2_ESA_INBOUND in software component FS-BP. This development package consists of objects that can be grouped under "Inbound Service Proxies for FS-BP in FND".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Relationship category &1 supports one-way relationships only |
| 002 | Relationship category &1 does not exist |
| 003 | Could not delete the alias &1 |
| 004 | Alias &1 already exists |
| 005 | Could only create or delete aliases |
| 006 | Change indicator &1 needs a data record in the table &2 |
| 007 | Intervals are not supported for roles |
| 008 | No existing address found for UIID &1 |
| 009 | Invalid change state ID for business partner &1 |
| 010 | You can transfer either a CTI or action codes for &1 |
| 011 | You do not have authorization to display the details for BP &1 |
| 012 | Business partner with number &1 exists already |
| 013 | Could not initialize general data for partner |
| 014 | Business partner with UUID &1 exists already |
| 015 | No changes were made |
| 016 | Business partner &1 already has address-independent communication data |
| 017 | BP &1 does not have any address-independent communication data |
| 018 | Alias &1 does not exist for business partner &2 |
| 019 | Invalid combination of action code &1 and &2 in nodes &3 and &4 |
| 020 | Action codes in nodes &1 and &2 must be the same |
| 021 | Action code &2 is not supported in node &1 |
| 022 | Action code no action expects a data record in table &1 |
| 023 | When you create &1, you must create &2 with at least &3 |
| 024 | &1 cannot be processed for &2 &3 |
| 025 | Action codes for nodes &1 and &2 must be the same if &3 is the same |
| 026 | Action code &1 is not permitted for international address version |
| 027 | Element &2 must be entered in node &1 |
| 028 | No relationships found for selection criteria |
| 029 | Business partner relationship &1 already exists |
| 030 | Business partner relationship does not exist |
| 031 | Business partner &1 does not exist |
| 032 | Validation: invalid query |
| 033 | Validation: invalid request |
| 034 | Result cannot be provided |
| 035 | Invalid change state ID for relationship &1 |
| 036 | Address data is missing for contact person relationship |
| 037 | Only one telephone number permitted for contact person relationship |
| 038 | Only one fax number permitted for contract person relationship |
| 039 | Only one e-mail address permitted for contact person relationship |
| 040 | Only one workplace address permitted for contact person relationship |
| 041 | Wildcard search (values &1) only permitted for interval code "1" |
| 042 | Wildcard search (values &1) is not allowed |
| 043 | You are not permitted to delete relationship &1 with the UPDATE service |
| 044 | Relationship &1 must not occur more than once in a call |
| 045 | &2 must not be set if &1 is "true" |
| 046 | Workplace data to be created already exists |
| 047 | Workplace data to be changed does not exist |
| 048 | Workplace data to be deleted does not exist |
| 049 | Telephone number to be created with ID &1 already exists |
| 050 | Telephone number to be changed with ID &1 does not exist |
| 051 | Telephone number to be deleted with ID &1 does not exist |
| 052 | Fax number to be created wiht ID &1 already exists |
| 053 | Fax number to be changed wiht ID &1 does not exist |
| 054 | Fax number to be deleted wiht ID &1 does not exist |
| 055 | E-mail address to be created wiht ID &1 already exists |
| 056 | E-mail address to be changed wiht ID &1 does not exist |
| 057 | E-mail address to be deleted with ID &1 does not exist |
| 058 | Combination of addresses with and without ADDR_GUID is not permitted |
| 059 | More than one address without OrganisationAddressUUID is not premitted |
| 060 | There must be at least one sentence of address data |
| 061 | Note to be created in language &1 already exists |
| 062 | Note to be changed in language &1 does not exist |
| 063 | Note to be deleted in language &1 does not exist |
| 064 | There is no address with OrganisationAddressUUID &1 |
| 065 | Invalid business partner relationship; field &1&2 has not been filled |
| 066 | Invalid combination of business partner's key elements |
| 067 | Invalid business partner relationship in &1 |
| 069 | Value in element &1 must not exceed &2 |
| 070 | Value &1 in element &2 (&3 node) must be a maximum of &4 characters long |
| 071 | Maximum length of an e-mail address is 241 characters |
| 072 | Letters or special characters are not permitted |
| 073 | Value &1 in element &2 (node &3) must be exactly &4 characters long |
| 074 | Value &1 is not valid for element &2 |
| 075 | No address data permitted for combination of BP category &1 and &2 |
| 076 | Do not fill node &2 if relationship category is &1 |
| 077 | Either set the "Unlimited" checkbox to true or fill the Max. Hits field |
| 078 | Value &1 is not permitted; use "I" only |
| 079 | Only 1, 3, 6, 7, 8 and 9 supported as the IntervalBoundaryTypeCode |
| 080 | Only "I" is supported as InclusionExclusionCode (in &1) |
| 081 | Either search by alias or by search text fields |
| 082 | &2 must not be filled when you are searching by &1 |
| 083 | &2, &3, &4 must not be filled when you are searching by &1 |
| 084 | Note &1: Lower limit &2 is higher than the upper limit &3 |
| 085 | "Upper Boundary" field must not be filled for interval code &1 |
| 086 | Node &1: Upper limit not filled |
| 087 | Business partner relationship still exists |
| 088 | Data has been edited in ECH/PPO |
| 089 | Only the digits &1 permitted |
| 090 | Lower limit &1 is larger than upper limit &2 |
| 091 | Node &1 must not be filled |
| 092 | "Lower Boundary" field must not be filled for interval code &1 |
| 093 | Text to be changed not found |
| 094 | First business partner has not been entered in relationship |
| 095 | Second business partner has not been entered in relationship |
| 096 | You are not permitted to enter a period for a time-independent rel. cat. |
| 097 | No nodes that determine the BP category have been filled |
| 098 | More than one node that determines the BP category have been filled |
| 099 | Enter the role code in format "nnnnnn-d"; for example: BUR004-0 |
| 100 | Role &1 cannot be created |
| 101 | Currency code at node "&1"("&3") and note "&2"("&4") have to be identic |
| 102 | The node &2 is only supported by the CategoryCode 2 (Organisations) |
| 103 | '&1' and '&2' cannot be filled at the same time |
| 105 | Extended XML does not work or Common is filled with Person, Org and Group |