SAP ABAP Data Element XST_AVMACT (IS-M: Control Order Update from Contract)
Hierarchy
☛
IS-M (Software Component) SAP MEDIA
⤷
IS-M (Application Component) SAP Media
⤷
JAS (Package) Application development R/3 Publishing Advertising System***
⤷
⤷
Basic Data
| Data Element | XST_AVMACT |
| Short Description | IS-M: Control Order Update from Contract |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XST_AVMACT | |
| Data Type | NUMC | Character string with only digits |
| 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 | OPM Update |
| Medium | 15 | Update OPM |
| Long | 40 | Order Update from Contract |
| Heading | 4 | Upd. |
Documentation
Definition
This allows you to control whether order data is updated in dialog once contract data has been changed.
Value range
Values from 0 to 7 are admissible whose three binary numbers are to be interpreted as follows:
1 Order update following saving in contract maintenance
2 Order update following saving in contract monitoring
3 Order update once a contract settlement has been saved
Further notes
Value 0 indicates that no order update has been performed in contract dialog processing. Orders are always updated:
- If they are processed in dialog (the updated version is only entered in the database using the "Save" function)
- Using the report RJHAUFAK that can be scheduled to run periodically in the background.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |