Hierarchy
⤷
⤷
Basic Data
| Data Element | TRMNOSRC |
| Short Description | Source of Transfer Number |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TRMNOSRC | |
| 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 | Srce:TrsNo |
| Medium | 15 | Source:Trnsf.No |
| Long | 22 | Source of Transf.No. |
| Heading | 10 | Srce:TrsNo |
Documentation
Definition
Specifies whether the external transmission number was transmitted by your EDI partner, or whether it was generated by your SAP system.
Use
If your EDI partner does not send a transmission, you have the option of having one generated by the system. The number can be taken either from the day's date or from the number of IDocs that make up the transmission.
SAP recommends that you only use this generation of transmission numbers for test purposes. Transmission numbers should usually be received from your partner.
Procedure
Examples
Dependencies
When taking the transmission number from the current date, you can define a time delay in the general parameters, so that the date change does not take place at 00:00, but at a different time.
This enables you to still assign IDocs that logically belong together, but arrive either side of midnight, to the same transmission number derived from the current date.
History
| Last changed by/on | SAP | 20030411 |
| SAP Release Created in |