SAP ABAP Data Element CONVERTER_CHECKOUT_DEPTH (Scope of the conversion structure)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ LO-PDM (Application Component) Product Data Management
⤷ CONV0C (Package) Customizing conversion
⤷ LO-PDM (Application Component) Product Data Management
⤷ CONV0C (Package) Customizing conversion
Basic Data
Data Element | CONVERTER_CHECKOUT_DEPTH |
Short Description | Scope of the conversion structure |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CONVERTER_CHECKOUT_DEPTH | |
Data Type | CHAR | Character String |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Depth |
Medium | 20 | Check Out depth |
Long | 25 | Check Out depth |
Heading | 30 | Check Out depth |
Documentation
Definition
Sets the scope of a BOM structure is part of a conversion.
Use
If the document belongs to a BOM structure the converter needs not only the original but also other files from the structure. Here you set how deep the structure is expanded and which files must be checked out.
&Dependencies%
- One original application file is converted into exactly one target file.
The conversion is automatically started when the status that is set in Customizing is reached and the document is saved. It can also be started using the transaction conv02 and the function module CONVT_CONVERT_AT_STATUS_CHANGE - Material BOM: All files of the document are read including BOM item and BOM header. Links to BOM items in the document are not exploded (expanded) and the conversion does not include them. There can be one target file for one source file and transformation matrices can be created for BOM items.
The conversion can only be started with the transaction conv03 or the function module CONV_API_CONVERT_BOM_ASSEMBLY (for example for CAD interface). - Material BOM references document structure: like material BOM with additional checks whether it is the header of a document structure. When it is the document structure is expanded at multiple levels and the original application files of the document are set up for the converter. Converted files and transformation matrices cannot be written to the documents.
The conversion can only be started with the transaction conv03 or the function module CONV_API_CONVERT_BOM_ASSEMBLY (for example for CAD interface). - The document structure (source) to target: The document structure is expanded on multiple levels and the files therein set up for the converter. The converter is started by the file in the header of the document structure. Only one converted file can be written to the header of the document structure.
The conversion can only be started with the transaction conv04 or the function module CONV_API_CONVERT_DOC_STRUCTURE (for example using the customer exit from DMS).
Notes
All original application files of all documents are read by the workstation application that is entered in the field WS Appl.
All documents with the same document type as the one indicated in the document type field are read when exploding material BOMs. When converting BOMs all original application files must be in a secure storage area of the SAP System (KPRO, vault) or none of them at all. Compare with the indicator local and always local.
Examples
- If you only want to convert individual objects of a certain document type that has a certain status choose the setting one original application file.
In this case only one original application file is checked out. - If you want to convert from a material BOM and the original application files under it in the BOM structure choose the setting MaterialBOM.
History
Last changed by/on | SAP | 19991014 |
SAP Release Created in |