COLLISION title: collision (BC-I18-UNI) (SAP Library - Glossary)
COLLISION category: I18N Unicode (BC-I18-UNI)
COLLISION explained:
Preparation of MDMP System conversion to Unicode.
Collisions may occur whenever a language key is incorrect in the database, e.g. when a word is used in two languages which use different code pages.
The conversion tool gets conflicting information about which code page to use for the conversion of a table row in:
TABCAT2 tables TABCAT1 tables with ambiguous language informationMore terms such as collision in Dictionary C.
- Manual Customer Exception List:
- Help preconversion phase, tables can be excluded from one or more scans by adding them to one of two exception lists: customer exception list default exception list The customer list is empty and can be collision definition.
- Manual Contingent Liability:
- Help The contingencies or rights of recourse arising from payment guarantees made, warranties, and bills of exchange. These items are displayed separately on the balance sheet collision explain.
- Manual Cost Object Hierarchy:
- Help cost object hierarchy contains a number of cost objects structured in hierarchical form. A cost object hierarchy can be used to analyze target costs, actual costs, and variances in situations where collision what is.
- Manual Confirmation Status Determination:
- Help sales scheduling agreement item that is determined when confirmations are created in the product view, product planning table or interactive backorder processing. The status shows whether the collision meaning.
- Manual Correspondence Package:
- Help Summary of multiple documents that are created in processing, in one single document collision abbreviation.