Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-PDM (Application Component) Product Data Management⤷
CE (Package) B2B Engineering
IMG Activity
| ID | SIMG_OLPR_CEPBOM | Define document types for document BOMs |
| Transaction Code | S_XB8_60000002 | (empty) |
| Created on | 20000918 | |
| Customizing Attributes | SIMG_OLPR_CEPBOM | |
| Customizing Activity | SIMG_OLPR_CEPBOM | Dokumentart für Stücklisten definieren |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_OLPR_CEPBOM |
In this activity you maintain the document types that are to be the headers in the BOMs and those that are to be the items. Only the pair of document types specified can be used within one document BOM. This document BOM can be used to structure your documents or as precursor for a material BOM.
Any type of document can have a BOM relationship with another document. The following are examples of the types of documents that can have a BOM relationship.
Equipment (EQU)- Individual, physical object that is to be maintained as an autonomous unit.
Bill of Material (BOM) - A complete, formally structured list of the components that make up a product or assembly. The list contains the object number of each component, together with the quantity and unit of measure.
Vendor (VEN) - Business partner from whom materials or services can be produced.
Material (MAT) - Good that is the subject of business activity.
Example
Requirements
If the document type is not contained in this table as a header, it is possible to assign any document type to it.
Standard settings
Recommendation
Activities
Further notes
Remember that a document BOM like othe types of BOMs only consists of one level. This that the item becomes the header in the next lower level. If you want to have multi-level document BOMs you should bear this in mind, and for instance, use the same document type for header and item and have several item document types for the same header document type.
The table CEPDOCBOMTYPES is extended to include a category for each FROM/TO assignment. The category serves as a description for the placeholder objects.
Category 0: Create function that defines which position type can be used for the header, implicitly defines that the FROM object is a BOM header, and that a TO placeholder object must be created along with a position containing the TO object and that it must be added to the BOM.
Category 1: Assign function allowing the user to search through a list of TO placeholder objects. It then creates a new BOM position containing the TO object and adds the position to the BOM.
Category 2: Designates which icon should be used in the tree after the first position is created.
Category 3: Indicates the maximum number of TO placeholders linked to FROM placeholders.
Category 4: Indicates the minimum number of TO placeholders linked to FROM placeholders.
Business Attributes
| ASAP Roadmap ID | ||
| Mandatory / Optional | ||
| Critical / Non-Critical | ||
| Country-Dependency |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_TDOCBOMTYPES | V - View | SM30 |
History
| Last changed by/on | SAP | 20001214 |
| SAP Release Created in | 46C |
