| BP750 |
Availability control for: & |
| BP751 |
Availability control is & |
| BP752 |
Check against first BS element with budget |
| BP753 |
Check against first budget object |
| BP754 |
Cover eligibility active |
| BP755 |
Availability control against total despite year-dependent master data |
| BP756 |
Caution: You are changing the hierarchy settings for avail. control -> |
| BP757 |
Availabty ctrl against total, despite abilty to only maintain annual vals |
| BP758 |
Caution: You are changing the hierarchy settings for avail. control -> |
| BP759 |
Perform reconstruction of releases and assigned values for &1/&2 |
| BP760 |
The assigned data for the posting is locked by user &1 |
| BP761 |
System error when locking the assigned data you processed |
| BP762 |
System error when accessing the lock table |
| BP763 |
Select a line with data |
| BP764 |
Select a line with data |
| BP765 |
PB: Check against first BS element with budget |
| BP766 |
PB: Check against first budget object |
| BP767 |
PB: Check against first assignment object |
| BP768 |
AB: Check against first BS element with budget |
| BP769 |
AB: Check against first budget object |
| BP770 |
AB: Check against first assignment object |
| BP771 |
The person chosen to approve is not the person responsible for the bdgt |
| BP772 |
The employee you have chosen is not responsible for the budget |
| BP773 |
The person chosen to give approval does not correspond to the std role |
| BP774 |
The person chosen to process does not correspond to the standard role |
| BP777 |
Budget structure is not correct |
| BP779 |
Activating cover eligibility is not possible |
| BP780 |
Cannot use commitment type profiles together with cover eligibility |
| BP781 |
Cover eligibility and assignment object cannot be used together |
| BP782 |
There are too few own assigned funds in superior element |
| BP783 |
Use of budget objects is necessary if cover eligibility is active |
| BP784 |
Use of budget objects is necessary if cover eligibility is active |
| BP785 |
Cover eligibility relationships are being demanded |
| BP786 |
Deleting cover eligibility profile &1 not allowed |
| BP787 |
Entry is invalid; &1 / &2 must be eligible for cover |
| BP788 |
Functional area and cover eligibility can not be used simultaneously |
| BP789 |
Entry is not valid; Cover eligibility must be the same in PB and CB |
| BP790 |
Entry is not permitted; it is still assigned to a commitment type profile |
| BP791 |
Entry not permitted; a cover eligibility profile is still assigned |
| BP795 |
Av. control error message converted to less severe response by customer |
| BP796 |
Availability control activated without "suitable" budget |
| BP797 |
Number of data of commitment item hierarchy (record type A): &1 |
| BP801 |
& & payment budget exceeded |
| BP802 |
& payment budget for year & exceeded |
| BP803 |
Item & payment budget exceeded |
| BP804 |
Item & payment budget exceeded |
| BP805 |
& & payment budget exhausted |
| BP806 |
& payment budget for year & exhausted |
| BP807 |
Item & payment budget exhausted |
| BP808 |
Item & payment budget exhausted |
| BP811 |
& & payment budget almost exhausted |
| BP812 |
& payment budget for year & almost exhausted |
| BP813 |
Item & payment budget almost exhausted |
| BP814 |
Item & payment budget almost exhausted |
| BP821 |
& & commitment budget exceeded |
| BP822 |
& commitment budget for year & exceeded |
| BP823 |
Item & commitment budget exceeded |
| BP824 |
Item & commitment budget exceeded |
| BP825 |
& & commitment budget exhausted |
| BP826 |
& commitment budget for year & exhausted |
| BP827 |
Item & commitment budget exhausted |
| BP828 |
Item & commitment budget exhausted |
| BP831 |
& & commitment budget almost exhausted |
| BP832 |
& commitment budget for year & almost exhausted |
| BP833 |
Item & commitment budget almost exhausted |
| BP834 |
Item & commitment budget almost exhausted |
| BP835 |
& Multiple revenue in the payment budget for year & exceeded |
| BP837 |
Item & multiple revenue in payment budget is exceeded |
| BP840 |
& Multiple revenue in the commitment budget for year & is exceeded |
| BP842 |
Item & multiple revenue in commitment budget is exceeded |
| BP850 |
All budget types must be the same for each line group |
| BP851 |
All value types must be the same per line group |
| BP852 |
All years of cash effectivity must be the same per line group |
| BP853 |
All budget subtypes must be the same per line group |
| BP854 |
The transaction currency and FM area currency entered differ |
| BP855 |
Commitment item types must be the same for sender and receiver |
| BP856 |
Budget object & cannot be deleted |
| BP860 |
Budgetary ledger is not active in FM area &, do not enter a posting date |
| BP861 |
Budgetary ledger is active in FM area &, enter a posting date |
| BP862 |
Enter a fiscal year that corresponds to the posting date |
| BP864 |
Enter a period that corresponds to the posting date entered |
| BP865 |
Sender and receiver periods must be the same |
| BP866 |
No decision reason for workflow & |
| BP867 |
Enter a decision reason corresponding to the activity |
| BP868 |
Setting for sender and receiver budget subtypes must be the same |
| BP869 |
Document & can only be processed in the workflow |
| BP870 |
First place the cursor on the required text line |
| BP871 |
Do not enter a document type: BL is not active in FM area & |
| BP872 |
Enter a document type: Budgetary ledger is active in FM area & |
| BP873 |
Number of data of commitment item hierarchy (record type A): &1 |
| BP880 |
You can only apply for budget for one object |
| BP881 |
Enter a valid currency in the currrency field |
| BP882 |
The network or network activity is not assigned to a WBS element |
| BP883 |
The budget release function is not supported for orders |
| BP884 |
You cannot delete the costing |
| BP885 |
Costings have already been created in this project using Project Builder |
| BP886 |
A costing has already been created for the order, using the master data |
| BP887 |
The costing could not be saved |
| BP888 |
An individual costing was already created for the order in planning |
| BPFS003 |
Enter a valid bank country |