Id | Title |
---|---|
BBP_SUS_BP047 | Registration ID &1 created |
BBP_SUS_BP048 | Data saved successfully! |
BBP_SUS_BP049 | No data found |
BBP_SUS_BP050 | Data sent successfully via e-mail |
BBP_SUS_BP051 | Business partner &1 is assigned to business partner &2 |
BBP_SUS_BP052 | Business partner &1 can be created again. Replicate again! |
BBP_SUS_BP059 | *----------------------------------------------------------------------* |
BBP_SUS_BP060 | No partner found with system: &1, function &2, and role &3 |
BBP_SUS_BP061 | Maintain the business partner ID types |
BBP_SUS_BP064 | Supplier &1 |
BBP_SUS_BP065 | User &1 |
BBP_SUS_BP066 | No business partner found for user &1 |
BBP_SUS_BP067 | Business partner &2 found in SUS for user &1 |
BBP_SUS_BP068 | User role &1 added |
BBP_SUS_BP069 | Error adding user role &1 |
BBP_SUS_BP070 | Error generating new password |
BBP_SUS_BP071 | New password for user &1 successfully generated |
BBP_SUS_BP072 | New password cannot be changed for user &1 |
BBP_SUS_BP073 | User &1 has no e-mail |
BBP_SUS_BP074 | No SRM administrator found |
BBP_SUS_BP075 | SRM administrator &1 has no e-mail |
BBP_SUS_BP076 | No notification text &1 found in language &2 |
BBP_SUS_BP077 | E-mail notification sent to &1 |
BBP_SUS_BP078 | Error sending e-mail notification to &1 |
BBP_SUS_BP079 | File &1 cannot be read |
BBP_SUS_BP080 | Error when reading file &1 |
BBP_SUS_BP081 | Business partner &1 does not have a number for system &2 |
BBP_SUS_BP082 | Business partner &1 has no users |
BBP_SUS_BP083 | &1 does not exist |
BBP_SUS_BP084 | Data written successfully to file &1 |
BBP_SUS_BP085 | Cannot find Business Systems |
BBP_SUS_ONEORDER000 | === Up to 029 reserved for generating One Order structures === |
BBP_SUS_ONEORDER001 | Invalid name of include structure &1 |
BBP_SUS_ONEORDER002 | Generation of scenarios locked by user &1 |
BBP_SUS_ONEORDER003 | Generation is in test mode |
BBP_SUS_ONEORDER004 | Invalid name for append structure & |
BBP_SUS_ONEORDER005 | An active append structure & already exists |
BBP_SUS_ONEORDER006 | Existing append structure & activated |
BBP_SUS_ONEORDER007 | The append structure &1 was generated for &2 |
BBP_SUS_ONEORDER008 | The append structure &1 cannot be generated for &2 |
BBP_SUS_ONEORDER009 | Error while generating catalog entry of append structure &1 |
BBP_SUS_ONEORDER010 | The append structure &1 cannot be activated for &2 |
BBP_SUS_ONEORDER011 | An unknown error occurred when structure &1 was generated |
BBP_SUS_ONEORDER012 | Simulated generation &1 for &2 |
BBP_SUS_ONEORDER013 | No active scenario was found, Customizing is missing |
BBP_SUS_ONEORDER014 | Scenario &1 was activated |
BBP_SUS_ONEORDER015 | Active scenario &1 &2 |
BBP_SUS_ONEORDER016 | No CRM transaction type defined for document &1 |
BBP_SUS_ONEORDER017 | No default CRM transaction type defined for document &1 |
BBP_SUS_ONEORDER018 | Invalid CRM transaction type &1 defined for document &1 |
BBP_SUS_ONEORDER019 | Check ended |
BBP_SUS_ONEORDER020 | Different status profiles in CRM transaction types for document &1 |
BBP_SUS_ONEORDER021 | Different status schemas in item categories for document &1 |
BBP_SUS_ONEORDER022 | Different status schemas for transaction type and item categories |
BBP_SUS_ONEORDER023 | No adminstration user is defined for scenario &1 |
BBP_SUS_ONEORDER024 | Administration user &1 requires an e-mail address |
BBP_SUS_ONEORDER025 | Specify an administration user |
BBP_SUS_ONEORDER026 | Specify a text module for supplier notification |
BBP_SUS_ONEORDER027 | Text module &1 does not exist |
BBP_SUS_ONEORDER029 | Specify scenario transaction type |
BBP_SUS_ONEORDER030 | Invalid document number |
BBP_SUS_ONEORDER031 | No scenario was specified |
BBP_SUS_ONEORDER032 | Requested &1 is not active. Activate scenario &2 |
BBP_SUS_ONEORDER033 | No data exists for this selection |
BBP_SUS_ONEORDER034 | Specify transaction type |
BBP_SUS_ONEORDER035 | Fill handle (internal error) |
BBP_SUS_ONEORDER036 | Specify transaction type and key of preceding document |
BBP_SUS_ONEORDER037 | Not possible to copy item. Check status |
BBP_SUS_ONEORDER038 | Not possible to copy all items |
BBP_SUS_ONEORDER039 | Invalid user. Enter valid user |
BBP_SUS_ONEORDER040 | Error calling module &1 |
BBP_SUS_ONEORDER041 | Information on supplier is missing in field &1 |
BBP_SUS_ONEORDER042 | Information on the scenario is missing in field &1 |
BBP_SUS_ONEORDER043 | Supplied scenario not active in CRM system |
BBP_SUS_ONEORDER044 | No orders found. Call of &1 |
BBP_SUS_ONEORDER045 | Information on process type missing in field &1 |
BBP_SUS_ONEORDER046 | Document number already exists. Choose another number |
BBP_SUS_ONEORDER047 | Requested scenario &1 is not active. Scenario &2 is activated |
BBP_SUS_ONEORDER048 | Checking of document number deactivated in supplier settings |
BBP_SUS_ONEORDER049 | == Messages for status function modules |
BBP_SUS_ONEORDER050 | Language was not found |
BBP_SUS_ONEORDER051 | Status text is not maintained in language &1 |
BBP_SUS_ONEORDER052 | No next status could be read |
BBP_SUS_ONEORDER053 | No status could be read |
BBP_SUS_ONEORDER054 | No status check could be read. Check table TJ30T |
BBP_SUS_ONEORDER055 | Transaction types were not found (table CRMC_M10_PT_MAPP) |
BBP_SUS_ONEORDER058 | No orders were selected |
BBP_SUS_ONEORDER060 | Incorrect date/time value in structure &1 in field &2 |
BBP_SUS_ONEORDER061 | Document &1 contains errors. Check in detail view |
BBP_SUS_ONEORDER062 | Error converting from OTF to PDF format |
BBP_SUS_ONEORDER063 | Form &1 does not exist |
BBP_SUS_ONEORDER070 | No entry for the e-mail address could be found |
BBP_SUS_ONEORDER071 | Address contains errors. Check data: &1. |
BBP_SUS_ONEORDER072 | The BADI implementation &1 was successfully activated |
BBP_SUS_ONEORDER073 | The BADI implementation &1 can be activated |
BBP_SUS_ONEORDER074 | The BADI implementation &1 was activated |
BBP_SUS_ONEORDER075 | The BADI implementation &1 can be deactivated |
BBP_SUS_ONEORDER076 | Field check for &1-&2 was adjusted accordingly |
BBP_SUS_ONEORDER077 | The field check for &1-&2 in CRMV_FIELDCHECK can be adjusted |
BBP_SUS_ONEORDER079 | = Messages from the history function modules |