SAP ABAP Data Element FLAG_TRIG (Flag for Activating the File Generation Triggers)
Hierarchy
☛
EA-RETAIL (Software Component) SAP Enterprise Extension Retail
⤷
SD-POS-OUT (Application Component) POS Interface - Outbound
⤷
WPOSA (Package) POS -Download Analysis- and Utility Programs
EA-RETAIL (Software Component) SAP Enterprise Extension Retail⤷
SD-POS-OUT (Application Component) POS Interface - Outbound⤷
WPOSA (Package) POS -Download Analysis- and Utility Programs
Basic Data
| Data Element | FLAG_TRIG |
| Short Description | Flag for Activating the File Generation Triggers |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FLAG | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Trig.Act. |
| Medium | 15 | Triggers Active |
| Long | 30 | File Generation Triggers Act. |
| Heading | 30 | File Generation Triggers Act. |
Documentation
Definition
Indicator for whether a trigger file should be created for the relevant ship-to party.
Use
Individual ship-to parties can create trigger files using the IDoc Copy Management tool. The IDoc names for the chosen ship-to party and message type are written to a file.
Dependencies
A port must be assigned in the partner description for the individual ship-to party (customer) and this port must also have a description (port description).
Example
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in | 200 |
