Hierarchy

⤷

⤷

IMG Activity
ID | PHIN_V_MPT_EXT | Make Customer-Specific Settings for Additional Measuring Points |
Transaction Code | S_E36_82000108 | (empty) |
Created on | 20070801 | |
Customizing Attributes | PHIN_V_MPT_EXT | Make Customer-Specific Settings for Additional Measuring Points |
Customizing Activity | PHIN_V_MPT_EXT | Make Customer-Specific Settings for Additional Measuring Points |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | PHIN_V_MPT_EXT |
Use
In this IMG activity, you can add fields for customer-specific measuring points to the Technical Object List on the Preparation & Generation tab page in both the takeover and handover applications. These enable you to exchange measurement readings (counter readings, for example, number of cycles) for additional measuring points (for example, cycles) with your business partners.
Requirements
You must have created data elements and the fields for the customer includes CI_PHINT_COUNTER and PHIN_S_WD2.
- In the include CI_PHINT_COUNTER, for each customer-specific measuring point (counter), you must:
- Define a field for the counter reading and a field for the timestamp of the reading
- Assign a data element with its specific field labels and the predefined domain FLTP_INOUT to the field for the counter reading.
- Assign a data element with its specific field labels and the predefined domain TZNTSTMPS to the timestamp field.
- In include CI_WD2_COUNTER, for each timestamp in include CI_PHINT_COUNTER, you must:
- Define a date field and a time field into which the timestamp is converted.
- Assign a data element with its specific field labels and the predefined domain PHIN_DOM_DATE to the field for the date.
- Assign a data element with its specific field labels and the predefined domain PHIN_DOM_TIME to the field for the time.
Standard settings
In the view PHIN_V_MPT_EXT1 you must define the following:
- A characteristic for the customer-specific measuring point (counter). Note that the measuring point characteristic must be unique for a particular technical object. This is the only way to ensure that the measuring point (counter reading) is assigned to the correct counter.
- The fields with which the additional data is to be exchanged. You cannot use the same field name twice, in other words, each field name must be unique.
- Set the indicator in the Counter column if the measuring point is a counter
You must implement the method CONVERT_TIMESTAMPS_EXT in BAdI BADI_PHIN_CUST_LOGIC. This is for the conversion of the timestamp to date and time and vice versa.
Activities
Example
The measuring point you want to add to the table is a counter so you can record the number of rough landings a particular aircraft makes. This could influence the frequency with which a particular part of the aircraft is maintained.
Characteristic for Measurement Point: RL
Field Name Cntr Reading: ZZ_RL
Field Name Timestamp: ZZ_RL_TSTAMP
Field Name Date: ZZ_RL_DATE
Field Name Time: ZZ_RL_TIME
Field for counter reading: ZZ_RL ZZ_RL FLTP_INOUT - Rough Landings
Field for timestamp: ZZ_RL_TIMESTAMP ZZ_RL_TIMESTAMP TZNTSTMPS
Field for counter date: ZZ_RL_DATE ZZ_RL_DATE DATS RL Date Rough Landings Date
Field for counter time: ZZ_RL_TIME ZZ_RL_TIME TIMS RL Time Rough LandingsTime
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | PHIN_V_MPT_EXT | 0 | HLA0009531 | Technical Objects |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
PHIN_V_MPT_EXT1 | V - View | SM30 |
History
Last changed by/on | SAP | 20071122 |
SAP Release Created in | 603 |