| /SAPSLL/PLUGINR3835 |
Customs warehouse transfer is not allowed; see long text |
| /SAPSLL/PLUGINR3836 |
Use transaction MB0A or MIGO to transfer customs warehouse material |
| /SAPSLL/PLUGINR3837 |
Plant/storage location combination not valid for posting customs WH mat. |
| /SAPSLL/PLUGINR3838 |
Transfer of customs warehouse material not supported without SD |
| /SAPSLL/PLUGINR3839 |
Goods receipt posting for customs WH material only for duty-paid stock |
| /SAPSLL/PLUGINR3840 |
Transfer not allowed; batches do not have country of origin |
| /SAPSLL/PLUGINR3841 |
Material &1 requires additional identification |
| /SAPSLL/PLUGINR3842 |
Product must be a component or a processed product |
| /SAPSLL/PLUGINR3843 |
Illegal change to base unit of measure in BAdI |
| /SAPSLL/PLUGINR3844 |
Illegal change to material stock in BAdI |
| /SAPSLL/PLUGINR3845 |
Customs warehouse extension only allowed w/zero stock for storage loc. |
| /SAPSLL/PLUGINR3846 |
Customs warehouse extension successful for plant/storage location |
| /SAPSLL/PLUGINR3870 |
No logs available |
| /SAPSLL/PLUGINR3871 |
Errors during call of module &1 |
| /SAPSLL/PLUGINR3872 |
Internal error during assignment of a field symbol |
| /SAPSLL/PLUG_IN_MD000 |
No partner selected using given selection criteria |
| /SAPSLL/PLUG_IN_MD001 |
No products selected using given selection criteria |
| /SAPSLL/PLUG_IN_MD002 |
Out of &2 business partners, &2 were transferred successfully |
| /SAPSLL/PLUG_IN_MD003 |
Out of &2 products, &2 were transferred successfully |
| /SAPSLL/PLUG_IN_MD701 |
Maintain a transaction type! |
| /SAPSLL/PLUG_IN_MD702 |
Entered application level & does not exist |
| /SAPSLL/PLUG_IN_MD703 |
Entered transaction type & does not exist (input help -> F4) |
| /SAPSMOSS/01000 |
******** Post ******************************************************** |
| /SAPSMOSS/01001 |
Follow-up function "Send SAP notification to SAP" does not exist |
| /SAPSMOSS/01002 |
Installation number unknown in SAPNet R/3 Frontend |
| /SAPSMOSS/01003 |
Text information for SAP does not exist yet |
| /SAPSMOSS/01004 |
No URL could be found for search term &1 |
| /SAPSMOSS/01005 |
Notification will be sent to the SAPNet R/3 Frontend when you save |
| /SAPSMOSS/01006 |
Follow-up function can only be executed once |
| /SAPSMOSS/01008 |
Notification has not yet been sent to SAP |
| /SAPSMOSS/01009 |
Notification has already been refreshed |
| /SAPSMOSS/01010 |
Notification being processed by SAP; no changes possible! |
| /SAPSMOSS/01011 |
Notification &1 has been refreshed |
| /SAPSMOSS/01012 |
Error while trying to connect to SAP |
| /SAPSMOSS/01013 |
You do not have authorization at SAP for notification &1 |
| /SAPSMOSS/01014 |
An error occurred while loading the notification |
| /SAPSMOSS/01015 |
You do not have authorization &1 at SAP |
| /SAPSMOSS/01016 |
Notification &1 is unknown at SAP |
| /SAPSMOSS/01017 |
You are not recognized as a user in the SAPNet R/3 Frontend |
| /SAPSMOSS/01018 |
SAP has a more current version of the notification |
| /SAPSMOSS/01019 |
Notification was not changed |
| /SAPSMOSS/01020 |
An error occurred while creating the note(s) |
| /SAPSMOSS/01021 |
Notification &1 is locked in the SAPNet R/3 Frontend |
| /SAPSMOSS/01022 |
Notification &1 is being processed by SAP |
| /SAPSMOSS/01023 |
Error while locking notification &1 |
| /SAPSMOSS/01024 |
Error while saving the notification |
| /SAPSMOSS/01025 |
Error while requesting the notification |
| /SAPSMOSS/01026 |
Notification is being requested |
| /SAPSMOSS/01027 |
You are not recognized as a customer at SAP |
| /SAPSMOSS/01028 |
Notification data is incomplete |
| /SAPSMOSS/01029 |
Invalid entries in field: &1 &2 &3 |
| /SAPSMOSS/01030 |
R/3 notification &1 was created in the CCC System |
| /SAPSMOSS/01031 |
You do not have authorization to send notifs to the SAPNet R/3 Frontend |
| /SAPSMOSS/01032 |
Notification has already been confirmed in the SAPNet R/3 Frontend |
| /SAPSMOSS/01033 |
Invalid entries in field: &1 &2 &3 |
| /SAPSMOSS/01035 |
The system could not find a user for you in the SAPNet R/3 Frontend |
| /SAPSMOSS/01040 |
No notification has been refreshed or newly created |
| /SAPSMOSS/01041 |
Notification &1 cannot be refreshed because it is currently locked |
| /SAPSMOSS/01042 |
Notification &1 is already completed and cannot be changed |
| /SAPSMOSS/01045 |
Notification &1 cannot be confirmed |
| /SAPSMOSS/01046 |
Error while confirming notification &1 |
| /SAPSMOSS/01047 |
Notification &1 cannot be confirmed |
| /SAPSMOSS/01048 |
None of the installations were assigned to a destination in the BAdI |
| /SAPSMOSS/01049 |
The selected installations could not be considered |
| /SAPSMOSS/01050 |
******** RFC module: Create notification ******************************* |
| /SAPSMOSS/01051 |
Installation &1 unknown |
| /SAPSMOSS/01052 |
SAP component &1 unknown |
| /SAPSMOSS/01053 |
Status &1 contains errors |
| /SAPSMOSS/01054 |
RFC error: &1 |
| /SAPSMOSS/01055 |
The message &1 &2 does not exist |
| /SAPSMOSS/01056 |
Message type &1 is not allowed |
| /SAPSMOSS/01060 |
BAdI incomplete: It is possible that not all messages can be updated |
| /SAPTRX/ASC000 |
No parameters available for determining application object type |
| /SAPTRX/ASC001 |
No application object type found for &1 &2 &3 |
| /SAPTRX/ASC002 |
No unique application object type found for &1 &2 &3 |
| /SAPTRX/ASC003 |
No application object type found for &1 |
| /SAPTRX/ASC004 |
Application object reference for &1 &2 in system &3 is locked by &4 |
| /SAPTRX/ASC005 |
SAP Event Management communication aborted; no AOTs defined |
| /SAPTRX/ASC006 |
No event management-relevant application object determined |
| /SAPTRX/ASC007 |
Logical system could not be determined |
| /SAPTRX/ASC008 |
Required control table &1 for AO type &2 not available |
| /SAPTRX/ASC009 |
Assigned application table &1 for AO type &2 is not available |
| /SAPTRX/ASC010 |
Application object type &1 not relevant for object &2 &3 |
| /SAPTRX/ASC011 |
Name tab for table &1 could not be read |
| /SAPTRX/ASC012 |
Application object type &1 relevant for object &2 &3 |
| /SAPTRX/ASC013 |
Condition &1 for application object type &2 incorrect |
| /SAPTRX/ASC014 |
Application object type determination stopped for object &1 &2 |
| /SAPTRX/ASC015 |
Control parameter determination error; check control parameter extraction |
| /SAPTRX/ASC016 |
Event handler for application object &1 &2 cannot be changed |
| /SAPTRX/ASC017 |
Event handler type for application object &1 &2 could not be determined |
| /SAPTRX/ASC018 |
Processing and communication aborted for AO type &1 |
| /SAPTRX/ASC019 |
Processing and communication to SAP Event Management completely aborted |
| /SAPTRX/ASC020 |
Drilldown is not possible from this field |
| /SAPTRX/ASC021 |
No SAP Event Management defined |
| /SAPTRX/ASC022 |
Key length of table &1 is defined as 0 for business process type &2 |
| /SAPTRX/ASC023 |
Data tables for application object type & successfully set up |
| /SAPTRX/ASC024 |
Objects for AO type &1 will be evaluated using condition &2 |
| /SAPTRX/ASC025 |
Event management relevance will not be checked for AO type &1 |
| /SAPTRX/ASC026 |
Event management relevance condition &1 could not be read |
| /SAPTRX/ASC027 |
Appl. object &1 skipped for AO type &2 due to settings |