SAP ABAP Data Element CRMT_PRODUCT_SRC_SYS (Logical System from Which Product Originates)
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷ CA-GTF (Application Component) General Application Functions
⤷ COM_ORDER (Package) General Objects in the Sales Transaction Environment
⤷ CA-GTF (Application Component) General Application Functions
⤷ COM_ORDER (Package) General Objects in the Sales Transaction Environment
Basic Data
Data Element | CRMT_PRODUCT_SRC_SYS |
Short Description | Logical System from Which Product Originates |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | LOGSYS | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table | TBDLS |
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 | Orig.Prod. |
Medium | 15 | Origin Product |
Long | 20 | Origin Product |
Heading | 10 | Orig.Prod. |
Documentation
Definition
Logical system (logical destination and client) from which the product originates.
Products available locally are identified in the CRM/EBP System by the GUID. For products for which no GUID exists, (for example, materials from the SAP R/3 System), the product number becomes unique in the CRM/EBP System by assigning the logical system from which they originate.
For products that do not exist locally, processing takes place in the EPB for example, if confirmations or invoices are created in a back-end system (for example, R/3). An additional scenario makes it possible for requirements to be sent into the EBP System from various planning systems. Here, they are grouped into orders, and then distributed into other systems.
History
Last changed by/on | SAP | 20040312 |
SAP Release Created in | 300 |