SAP ABAP Data Element W_URSAC_BS (Module that has caused the listing)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ WSOR (Package) IS-R: Assortments
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
WSOR (Package) IS-R: Assortments
Basic Data
| Data Element | W_URSAC_BS |
| Short Description | Module that has caused the listing |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WSORTK | |
| Data Type | CHAR | Character String |
| Length | 18 | |
| Decimal Places | 0 | |
| Output Length | 18 | |
| Value Table | WSOH |
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 | Module |
| Medium | 15 | Module |
| Long | 20 | Module |
| Heading | 18 | Module |
Documentation
Definition
Listing conditions are generated by a variety of functions. However, assortment modules are always used. Either a profile module is used automatically or an assortment module is specified explicitly (standard, exclusion, promotion, layout, or rack jobber modules).
To save space, the module that has caused the listing is not named in the listing condition key, since the cause is readily identifiable from other fields.
The number of the module used for the actual listing condition is specified in field WLK1-URSAC.
Example:
Step 1:
Listing via (profile) module 4711
Store Material From To Module Counter
0815 ABC 01.01. 31.12. 4711 0001
History
| Last changed by/on | SAP | 19980218 |
| SAP Release Created in |
