SAP ABAP Data Element N301MSGSZ (IS-H HCM: Max. Size Permitted for EDI Message in KB)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NBAS (Package) Appl. development Hospital System master data, catalogs
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NBAS (Package) Appl. development Hospital System master data, catalogs
Basic Data
Data Element | N301MSGSZ |
Short Description | IS-H HCM: Max. Size Permitted for EDI Message in KB |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | NUMC10 | |
Data Type | NUMC | Character string with only digits |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | MaxMsgKB |
Medium | 15 | Max. Msg. Size |
Long | 28 | Max. Message Size in KB |
Heading | 10 | MaxMsgKB |
Documentation
Definition
You need only make a specification here if the EDI procedure has explicitly stipulated a restriction on the length of individual messages which do not comply with the stucture definition of a message.
This restriction is relevant for Singapore only.
If there is no description as to how these messages exceeding the maximum length are to be handled, the system assigns them the status "not sent and incomplete or errored" and does not include them in the next dispatch run.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |