SAP SD: Working with condition records
![]() |
![]() |
![]() |
Title of test:![]() SAP SD: Working with condition records Description: Unit 3: Working with condition records_Book3 |




New Comment |
---|
NO RECORDS |
The list layout is specified by positioning and sorting the fields, which appears in the selected tables in one of which three Pricing report sections. Page Header: A page break occurs when a value changes. Group Header: A new line heading is generated for each table analysed. Items: Detailed record information is provided. Condition records can be maintained across all condition types and condition tables. Correct. Incorrect. Condition maintenance has two maintenance interfaces. Correct. Incorrect. The newer condition maintenance function can be configured using area menus. Correct. Incorrect. New condition records can be created with reference to existing condition records. Correct. Incorrect. Price change function allows to maintain multiple condition records simultaneously. Correct. Incorrect. Multiple condition records can be created by copying an existing condition record. Correct. Incorrect. Copying rules are maintained in Customising. If we are copying customer specific price condition record, the standard system provides the following two options. Create the target conditions over a specified range of customer numbers. Create the target conditions over a specified range of material numbers. Create the target conditions over a specified range of order numbers. We can maintain long texts in the condition records for pricing and agreements such as. Rebates. Sales deals. Promotion. Text is not copied when condition records created with reference. Correct. Incorrect. Whether text control offers customising to copy the long texts from condition records to the documents. Yes. No. The net prices are determined by simulating billing document. Correct. Incorrect. We can create and use condition indices to search for condition records that were created for a variety of condition types and condition tables. Correct. Incorrect. We can allow a release procedure to be used when a condition table is created by selecting the With release status checkbox. Correct. Incorrect. The release status is predefined. Which of the following status are defined. Relased. Blocked. Released for price simulation (Net price list). Release for planning and price simulation (Planning in CO-PA). Open. The calculation type determines how prices or discounts and surcharges are calculated for a condition. Correct. Incorrect. The release status is set indirectly by defining a processing status in Customising for pricing and assigning a release status to it. Correct. Incorrect. |