COM_PARTNER - Partner Processing Messages
The following messages are stored in message class COM_PARTNER: Partner Processing Messages.
It is part of development package COM_PARTNER in software component CRM-BF-PD. This development package consists of objects that can be grouped under "General Partner Processing".
It is part of development package COM_PARTNER in software component CRM-BF-PD. This development package consists of objects that can be grouped under "General Partner Processing".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Inconsistent table status |
| 001 | Partner &1 may not be entered manually! Check determination procedure &2! |
| 002 | Error in updating object &1 |
| 003 | You do not have ACE authority for partner &1 |
| 004 | Search parameters for partner &1 insufficient; enter more parameters |
| 005 | Corresponding partner function for function category &1 missing! |
| 006 | |
| 010 | Circle reference for partner function &1 (access sequence &2, access &3) |
| 011 | Only partner functions for scenario displayed |
| 027 | There is no BP relationship category for partner function category &1 |
| 028 | Relationship category &1 is not assigned to any partner function category |
| 031 | ***** PARTNER COMPETITOR PRODUCT CHECK MESSAGES (till 49)***** |
| 032 | Competitor Product &1 does not exist in the system |
| 033 | Enter a competitor product |
| 034 | Maintain a number between 0 and 100 for probability of success |
| 035 | Enter a currency |
| 036 | Remove duplicate entries for competitor product |
| 037 | Product &1 is not a competitor product |
| 038 | Maintain competitor product ID to maintain other comp. product details |
| 039 | Competitor &1 is not maintained for competitor product &2 |
| 050 | *** ERRORS IN DIALOG FUNCTIONS ***************************************** |
| 051 | Wrong parameters entered when changing address online |
| 100 | Field &1 is not available for partners |
| 101 | Attribute &1 (Semantic &2) is not available in &3 |
| 102 | No changes possible without entering a partner det. procedure |
| 103 | No more changes can be made to address field (&1) |
| 104 | Incorrect parameter transfer (&1) |
| 105 | Creating a partner without partner values not possible |
| 106 | Entry not found in object buffer |
| 107 | Entry not found in object buffer |
| 108 | Error when changing an entry in the object buffer |
| 109 | Entry not found in database buffer |
| 110 | Entry not found in database |
| 111 | At least one entry not found in database buffer |
| 112 | Partner determination procedure &1 not found |
| 113 | Address of partner function &1 may not be changed |
| 114 | Partner function with internal identification &1 does not exist |
| 115 | Partner function &1 is not allowed at this point |
| 116 | Partner of partner function &1 could not be changed here |
| 117 | Assignment of partner function &1 cannot be changed here |
| 118 | Attribute &1 (&2) is not available for partner function &3 |
| 119 | Enter &2 &1 &3 |
| 120 | Too many &1 entered; remove &2 &3 |
| 121 | No sales data can be determined for partner &1 (&2) |
| 122 | No pricing data could be determined for partner &1 (&2) |
| 123 | No shipping data could be determined for partner &1 (&2) |
| 124 | No classification data could be determined for partner &1 (&2) |
| 125 | No sales tax data could be determined for partner &1 (&2) |
| 126 | &1 with number &2 does not exist |
| 127 | Address of partner &1 (&2) does not have an address type |
| 128 | Address type &1 for partner &2 (&3) is not known |
| 129 | Address type &3 entered as default for partner &1 (&2) |
| 130 | Change of address numbers with adress source entry possible |
| 131 | Source of address for partner function &1 (assignment 2) not known |
| 132 | Address field &1 not available for address type &2 |
| 133 | Address changes for partner function &1 (assignment &2) not possible |
| 134 | Changes to address of type &1 not possible |
| 135 | Partner &1 (&2) is not an employee |
| 136 | Partner &1 (&2) is neither an employee nor an organizational unit |
| 137 | Partner &1 (&2) is not a competitor |
| 138 | Partner &1 (&2) is not a bidder |
| 139 | Partner &1 (&2) is not a vendor |
| 140 | No partner determination procedure determined for item category &1 |
| 141 | No partner determination procedure determined for business trans. &1 |
| 142 | Partner &1 may not be used in partner function &2 |
| 143 | Partner &1 (&2) is not a portal provider |
| 144 | Partner &1 (&2) is not clear (remove an entry) |
| 145 | &1 &2 (&3) is not a business partner |
| 146 | You may not use the private address of &1 (&2) |
| 147 | &1 (&2) is not specified |
| 148 | Partner function &4 is designed for &1 (&2 &3) |
| 149 | Partner determination was interrupted by an incorrect partner |
| 150 | Partner available for selection |
| 151 | Enter mandatory partner |
| 152 | Partners have alternative addresses |
| 153 | There are no filter values for BAdI enhancements |
| 154 | Filter value for entry &1 &2 &3 does not exist. |
| 155 | Partner function &1 may not be used in this document |
| 156 | Partner &1 (&2) is marked for deletion |
| 157 | Use the business partner &3 as a successor to &2 &1 |
| 158 | &2 &1 may not be used |
| 159 | The &2 &1 may not be contacted |
| 160 | &2 &1 has an order block (&3) |
| 161 | &2 &1 has a sales area dependent order block (&3) |
| 162 | &2 &1 has a delivery block (&3) |
| 163 | &2 &1 has a sales area-dependent delivery block (&3) |
| 164 | &2 &1 has a billing block (&3) |
| 165 | &2 &1 has a sales area dependent billing block (&3) |
| 166 | Check whether &2 &1 can be entered |
| 167 | &1 &2 (&3) is not a group hierarchy |
| 168 | Group hierarchies (&1) may not be used as &2 |
| 169 | Only group hierarchies can be used as &2 |
| 170 | &2 (&1) should be a pricing-relevant group hierarchy |
| 171 | &2 &1 is not a typical group hierarchy category |
| 172 | Partner Attribute &1 DOes Not Exist |
| 173 | Attribute value &1 is not provided for attribute &2 |
| 174 | Attribute group &1 does not exist |
| 175 | Attribute &1 is not assigned to attribute group &2 |
| 176 | Partner relationship category &1 does not exist |
| 177 | &2 &1 has status (&3) |
| 178 | No partner function for category &1 in determination procedure &2 defined |
| 179 | Select alternative proposal |
| 180 | Select a partner |
| 181 | Invalid user &1 (&2), specify valid business partner |
| 182 | Partners have alternative addresses |
| 183 | Partner &1 (&2) is not a contact person |
| 184 | Competitor product &1 already assigned to competitor &2 |
| 185 | Maintain a competitor for competitor product &1 |
| 186 | Partner function &1 is unavailable. |
| 200 | Text entry required for partner function |
| 201 | Enter a valid partner function |
| 202 | There is no selection to be made for partner quantity |
| 203 | No alternatives could be determined. |
| 204 | No alternative addresses could be determined. |
| 250 | Address not found (&1 &2) |
| 251 | Wrong parameters when calling up for copying a ZAV address |
| 252 | Wrong parameters when calling up for maintaining current address data |
| 253 | User of partner processing (&1) not recognized |
| 254 | Address type entered (&1) is unknown |
| 255 | Address use cannot be written without document identification |
| 256 | Access sequence &1 not found |
| 257 | Deadlock exists in partner det. proc. &1; determination is not possible |
| 258 | Function types/scenarios not available in system |
| 259 | Error when maintaining address |
| 260 | Error when deleting an address |
| 261 | Partner entered not found for comparison |
| 262 | Document header entered is not available for compressing partners |
| 263 | Error when compressing partner set |
| 265 | Errors when processing address |
| 300 | *** BPT special development for communication *** |
| 301 | Error when creating assets |
| 302 | All assets created successfully |
| 303 | Error when creating asset <&1> |
| 400 | Multiple partners exist with this description |
| 401 | Multiple hierarchy nodes exist with this description |
| 500 | *** Messages for wizards ********************************************* |
| 501 | Choose another name since partner determinat. procedure &1 exists already |
| 502 | Scenario "&" does not support any determination procedures |
| 503 | Choose another partner function for semantics &1 (&2 is not appropriate) |
| 504 | Use partner function &1 only once (multiple assignment) |
| 505 | Choose another internal key (&1 exists already) |
| 506 | The maximum occurrence of partner function &1 was adjusted |
| 507 | Select at least one user |
| 508 | Contradictory requirements; remove one user (for example, &1) |
| 509 | Requiring display variants for obj.&1 and &2 is contradictory |
| 510 | Key &1 does not correspond with the customer name space (Y*, Z*, 9*) |
| 511 | Enter a name for the partner determination procedure. |
| 512 | Territory &1 does not match &2 &3 |
| 513 | Territory &3 does not exist (&2 &1) |
| 550 | *** Messages for consistency checks ************************************* |
| 551 | Contradictory requirements w/ ref.to mandatory funct. &3 (obj. &1 and &2) |
| 552 | Contradictory requirements w/ ref. to occurrence &3 (object &1 and &2) |
| 553 | Select at least one partner determination procedure for checking |
| 554 | There are no inconsistencies according to the check. |
| 555 | It was not possible to check partner determ. procedure &1 for deadlocks. |
| 556 | Partner function &1 must not be used for object &2. |
| 557 | Partner function &1 is not defined correctly. |
| 558 | A partner function of function category &1 is mandatory in object &2 |
| 559 | Only one partner function of function category &1 is allowed |
| 560 | Partner function &3 must occur &4 times in object &2 |
| 561 | Partner function &3 must only occur &4 times at maximum in object &2 |
| 562 | Partner function &3 must occur exactly &4 times in object &2 |
| 563 | Changeability of partner function &1 is not as required. |
| 564 | Changeability of address of partner function &1 is not correct. |
| 565 | Calendar maintenance for partner function &1 is not as recommended |
| 566 | For usage in object &2 a partner function of category &1 is recommended. |
| 570 | Enter either determination procedure or partner function category |
| 600 | Partner &1 is not in the hierarchy of corporate channel partner &2 |
| 601 | Source &1 is unavailable for sequence number &3 in access sequence &2. |
| 602 | Specify the source details for sequence number &2 in access sequence &1. |
| 800 | Identification / short text entered already exists |
| 801 | Specify a key |
| 802 | Not all source parameters permitted for this source |
| 803 | Enter a partner function, function category and scenario or org unit |
| 804 | Function type and scenario must be entered together |
| 805 | Enter a partner function, function category or OU for this source |
| 806 | No parameters allowed for this source |
| 807 | Function type &1 is not provided in scenario &2 |
| 808 | A function type is necessary for defining a partner function |
| 809 | For this source, the function type "contact person" must be used. |
| 810 | At least one determination rule must be entered for this source. |
| 811 | Enter a description. |
| 812 | Enter a description that has not yet been used |
| 813 | Multiple mapping to partner function (&1) can lead to problems |
| 814 | Enter a partner function, or function category |
| 815 | Relationship type does not fit the partner function category |
| 816 | Partner access not possible |
| 817 | No main partnerfound. |