Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
| Data Element | SEQ |
| Short Description | Table number |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SYBIN4 | |
| Data Type | INT4 | 4-byte integer, integer number with sign |
| 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 | Table |
| Medium | 15 | Table no. |
| Long | 20 | Table no. |
| Heading | 55 | Table number |
Supplementary Documentation - SEQIN 0001
Use
This field is used to determine the name of the sequential file used by the initial account assignment program to store the data it creates.
Procedure
If the Travel Management System is linked to the FI System by ALE, the default name in the standard system is TRVFI. You can, of course, overwrite this name at any time. The target (FI) system automatically determines the global directory, which is added to the file name as a prefix. This new file name is then used to store the transferred work file.
If the two systems are not linked by ALE, the default work file name is TRVFI with the directory as the prefix.
Dependencies
Supplementary Documentation - SEQIN 0002
Use
Name of the work file which is created by the program RPRAPA00 and converted into a batch input session by the follow-up program RFBIKR00. When this batch input session is processed, vendor master records are created, changed or locked.
Procedure
Examples
Dependencies
Supplementary Documentation - SEQNA 1700
Use
If the text takes up several lines, each line is assigned a sequential number.
Procedure
Examples
Dependencies
Supplementary Documentation - SEQNO_512E0001
Use
You use the group and subgroup to determine in which order the information in the window is printed. All the information within a window, belonging to the same group and subgroup, is printed sequentially.
Supplementary Documentation - SEQNP 0001
Use
You can make several entries for one wage type.
This allows you to assign a wage type to several windows, and to cumulate a wage type in different wage types.
Procedure
Example
Dependencies
Supplementary Documentation - SEQNP 0002
Use
Enter a sequential number to define the order of wage types in the group.
Procedure
Example
Dependencies
Supplementary Documentation - SEQNP 0003
Use
You can use sequential numbers to store several consecutive breaks for one break schedule.
Procedure
Examples
Dependencies
Supplementary Documentation - SEQNP 0004
Use
A daily work schedule selection rule can consist of several individual rules. The individual rules are numbered sequentially.
The system works through the rules sequentially until it finds one which is appropriate.
Please note: Subsequent rules are not processed.
Procedure
Examples
Dependencies
Supplementary Documentation - SEQNP 0005
Use
The sequential number allows you to define the order in which the fields for the organizational key are called.
Procedure
Examples
Dependencies
Supplementary Documentation - SEQNU 0003
Use
T52C2
Procedure
Examples
Dependencies
Supplementary Documentation - SEQNU 0004
Use
T52C3
Procedure
Examples
Dependencies
Supplementary Documentation - SEQ_FILE 0001
Use
SEQ-NAME is interpreted as name of a sequential dataset. The search is carried out in the directory entered in the parameter DIR-NAME.
Procedure
Enter the name of the file here that contains the data to be copied.
Examples
Dependencies
Consider upper/lower case.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
