Hierarchy
ECC-DIMP (Software Component) DIMP⤷
IS-AD (Application Component) Aerospace & Defence Industry Solution⤷
AD_ROT_CALC (Package) Stock Calculation: Rotables & Expendables
Basic Data
| Data Element | RF |
| Short Description | Rotable Float / Expendable Requirement Quantity |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ORFCALC1 | |
| Data Type | DEC | Counter or amount field with comma and sign |
| Length | 16 | |
| Decimal Places | 6 | |
| Output Length | 20 | |
| 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 | RF |
| Medium | 17 | Rotable Float |
| Long | 20 | Rotable Float |
| Heading | 17 | Rotable Float |
Documentation
Definition
Identifies the number of spare parts required in the pipeline (hangar - transport - homeshop - transport - stock - hangar)
For a rotable:
- Indicates the rotable float
For a expendable:
- Indicates the expendable requirement quantity
In the case of Initial Provisioning, this value identifies the number of serviceable spare parts required initially on stock.
The value regards the stochastic demand because it depends on the service level.
Supplementary Documentation - RFCDEST 0001
Use
This RFC destination identifies the trusted system. You may not change the destination.
Procedure
Examples
Dependencies
Supplementary Documentation - RFCDEST 0002
Use
RFC destination pointing to an SSF server program.
Procedure
Examples
SAPSSFATGUI SAPSSFATDEST
Dependencies
Supplementary Documentation - RFCDEST 0003
Use
Enter an RFC destination of a different system, if the transactions of the role are to be started in this other system.
To transfer menu entries from another system via an RFC connection, enter a target system and choose From the SAP Menu. In the dialog box you can specify if you want to transfer the menu in a local system or via a remote system. If you choose a remote system, the SAP menu of the remote system is offered to you.
If you want to navigate in the SAP GUI via the SAP Easy Access menu, only RFC destinations should be used that have been created according to the trusted system concept. This ensures that the target system works with the same user.
Alternatively, a variable can also be specified in field Target System, that links to an RFC destination. Variables are assigned to RFC destinations in transaction SM30_SSM_RFC.
To distribute the role, choose Distribute. If the text Distribution Incomplete appears, you should perform the distribution again. The authorization data of the role is not distributed. Therefore the authorization data of the roles has to be updated in the target system.
If the field remains empty, the transactions are started in the same system in which the user is logged on.
Dependencies
Example
Supplementary Documentation - RFCDEST 1
Use
This RFC destination identifies the trusted system. You may not change it.
Procedure
Examples
Dependencies
Supplementary Documentation - RFCDEST 3333
Use
The RFC destination contains the connection data to the telephony server.
You can enter an existing RFC destination or select RFC destination to branch to the transaction to create RFC destinations.
Dependencies
Example
Supplementary Documentation - RFCDEST 9000
Use
In the Alert Monitor, the RFC destination identifies the connection to the remote monitoring segments.
The monitoring architecture assigns the name automatically for R/3 servers in the local R/3 System and host and database segments.
In remote systems and servers, the name is specified using the Remote Monitoring function in Transaction RZ21.
In either case, you can change the RFC destination name here. If you do, you must ensure that the destination has been entered as as remote destination in the RFC maintenance transaction (SM59).
Procedure
Examples
Dependencies
Supplementary Documentation - RFCSNC 0001
Definition
The component SNC (Secure Network Communications) provides additional security, for example, through the encryption of the transferred data and reciprocal authentication of the communication partners.
To use SNC you need to have an external security product and SNC must be set in the Customizing profile (for example, see parameter snc/enable).
If SNC is in use, in the SNC mode setting you can choose to select the additional security functions for this destination. If you choose these, further SNC options must be maintained. Choose the menu path: Destination -> SNC Options.
If SNC is not in use, the option to set the SNC mode is deactivated.
Dependencies
Example
Supplementary Documentation - RFCSNC 0100
Definition
The component SSL (Secure Socket Layer) enables additional protection for example, through the encryption of transferred data and secure reciprocal authentication of the communication partners.
The use of SSL requires an external security product and must be set in the Customizing profile.
Dependencies
Supplementary Documentation - RFILE_RP 0001
Use
Enter the name of the dataset in which the time tickets are stored.
Procedure
Examples
Dependencies
Supplementary Documentation - RFORM 0001
Examples
The surface area of a circular sheet of metal is calculated via the formula defined under formula key F2 in Customizing (BOMs).
Formula key: F2
Formula : Size1 * Size1 * pi
Supplementary Documentation - RFORM 0010
Procedure
Please note:
- If you do not enter a formula key, the sizes entered are multiplied together.
- If you enter a formula key, the algorithm defined in Customizing (Bills of material ) under this formula key is used to calculate the quantity.
Supplementary Documentation - RFPLN_D 0001
Use
Number of an invoicing plan, intended to serve as a reference. When you create an invoicing plan, the dates and values in the reference are updated and copied to the invoicing plan. The basis for date determination is the start date of the transaction/component. The basis for the value transfer is the amount in the transaction/component
In Customizing, you can store a standard invoicing plan that can then be used automatically as a reference when an invoicing plan is created.
Procedure
Examples
Dependencies
Supplementary Documentation - RFPNR 0001
Use
If you enter a personnel number, a reference is created between the current personnel number and the one you have just entered.
The system carries out the following actions automatically:
- The references between personnel numbers are defined by infotype 0031. Data is either added to the infotype or a new infotype is created for all personnel numbers linked in this way.
- The current personnel number may have infotype records for which the Copy infotype attribute is set in customizing. These infotype records are copied to the newly created personnel number.
Supplementary Documentation - RFPNR 0002
Use
Infotype 0121 Reference Personnel Number Priority enables you to determine the sequence in which the payroll runs for an employee's reference personnel numbers. This sequence is called the priority. The reference personnel number with the highest priority (priority = 1) is the first for which the payroll runs.
To define this sequence, specify the reference personnel numbers in the order of priority that you require.
Supplementary Documentation - RFPNR 0003
Use
This infotype is used to define a sequence in which the reference personnel numbers are accounted in a payroll run.
This sequence is called a priority.
This column contains the priority of the previous infotype record.
A flag is set in the checkbox for reference personnel numbers chosen for the current priority.
Supplementary Documentation - RFPNR 0004
Use
The infotype defines the sequence in which reference personnel numbers are accounted.
This sequence is referred to as priority.
This column shows all reference personnel numbers from the Reference Personnel Numbers infotype (0031). Choose a suitable priority for these personnel numbers.
The reference personnel numbers which have been chosen for the current priority are marked.
History
| Last changed by/on | SAP | 20050301 |
| SAP Release Created in | 46C2 |
