BOS03 - Costing: Sales Documents with BOS

The following messages are stored in message class BOS03: Costing: Sales Documents with BOS.
It is part of development package AD_BOS_01 in software component IS-EC-BOS. This development package consists of objects that can be grouped under "Customer Bills of Services (IBU A&D/E&C)".
Message Nr
Message Text
001No costing available for bill of services &1 &2
002Note line and service line w. unrestr. qty will not be copied to costing
003BOS contains no hierarchies or services
004No service lines exist that can be costed
005Costing tool not determined
006Descr. for structure &1 does not exist in logon language &2
007Descr. for addition/deduction &1 does not exist in logon language &2
008Cost transfer not possible; cond. types missing in pricing procedure &1
009Definition of cost component structure &1 is incomplete
010Cost component structure &1 has not been assigned to pricing procedure &2
011Cost component &1 (struct. &2) has not been assigned to pricing proc. &3
012Condition type &1 does not exist in pricing procesure &2
050Disallowed status change for addition/deduction procedure &1, version &2
100***** Messages from ECP **************
101Place your cursor on the line to be copied
102Changes were copied
103Action cancelled: no changes saved
104Select a base costing item
105You have selected more than one costing item: please only select one
106Explosion not possible: selected item is not base object costing
107Action cancelled; costing item cannot be changed
108Account assignment cannot be determined
109Quantity &1 &2 cannot be changed in simulation/mass change mode
110Key field missing for data record &1
111Data record in services missing for data record &1
112Costing is not allowed for Outline/Main Item
113Both cost item and cost model is not possible for service data record &1
114Invalid costing varaint(please check your entry)
115Costing is attached to Outline
116Cost model value exist without cost model
117Condition Value is too big
140This functionality is obsolete.Please refer to SAP Note 2201989.
Privacy Policy