PM Tables and Transaction

HI...
Plz provide the Plant maintenance(PM) Tables and Transaction.
And detais about PMIS?? Use of it??
thanks..

Hi,
PM T codes and PM Tables
Equipement-- Maintable-EQUI
Functiuonal location-     IFLOT
Serial number             -SERI
Material master         MATNR
IE01                 Create Equipment
IL01                 Create Functional Location
IB01                 Create Equipment BOM
IQ01                 Create Material Serial Number
MM01               Material Master
IB 01, IB11       Bills of materials
IW21 - Notification creation
IW31- PM order IA07 Display General Task List IA03 Display Equipment Task List IA13 Display Functional Location Task List IR03 Display Work Centre KO88 Settle Order (Single) IW32 Change Work Order IW31 Create Work Order IW33 Display Work Order IW38 Work Order List Editing - Change IW39 Work Order List Editing - Display IW40 Work Order List Editing - Display Multi Level ME21 Create Purchase Order (pre R4.6) ME21N Create Purchase Order (R4.6 onwards) IP41 Create Single Cycle Plan (R4 onwards) IE02 Change Equipment IE01 Create Equipment IE03 Display Equipment IE05 Equipment List Editing - Change IE08 Equipment List Editing - Display IW42 Overall Completion Confirmation IW26 Create Notification QS42 Display Catalog ML81 Create Service Entry Sheet MM03 Display Material CS03 Display Material BOM IW13 Material Where Used List IW66 Change Notification List of Tasks IW67 Display Notification List of Tasks IW22 Change Notification IW23 Display Notification IH01 Display Functional Location Structure MB11 Goods Movement MB31 Goods Receipt IW8W Goods Receipt for Refurbishment (R4 onwards) IP02 Change Maintenance Plan IP03 Display Maintenance Plan IP10 Schedule Maintenance Plan IP30 Deadline Monitoring IP11 Change Maintenance Strategy IP12 Display Maintenance Strategy IP19 Maintenance Scheduling Overview Graphic IP24 Maintenance Scheduling Overview List IW28 Notification List Editing - Change IW29 Notification List Editing - Display IW30 Notification List Editing - Display Multi Level IW64 Change Notification List of Activities IW65 Display Notification List of Activities IW68 Change Notification List of Items IW69 Display Notification List of Items IQ03 Display Serial Numbers IW24 Create Notification IP42 Create Strategy Maintenance Plan (from R4 onwards) IW25 Create Notification IL02 Change Functional Location IL01 Create Functional Location IL03 Display Functional Location IL05 Functional Location List Editing - Change IL06 Functional Location List Editing - Display IW41 Time Confirmation - Indvidual Entry IW48 Time Confirmation - Collective Entry with Selection IW44 Time Confirmation - Collective Entry no Selection IA11 Create Functional LocationTask Lists IA12 Change Functional Location Task List IL02 Change Functional Location IA05 Create General Task List IA06 Change General Task List IA01 Create Equpment Task List IA02 Change Equipment Task List IE03 Display Equipment IR01 Create Work Centre IR02 Change Work Centre CA85 Replace Work Centre IP13 Strategy Package Sequence IP14 Strategy Package Sequence IP04 Create Maintenance Item IP05 Change Maintenance Item IP06 Display Maintenance Item IP17 Maintenance Item List Editing - Change IP18 Maintenance Item List Editing - Display IP02 Change Maintenance Plan IP03 Display Maintenance Plan IP15 Maintenance Plan List Editing - Change IP16 Maintenance Plan List Editing - Display IK11 Create Measurement Documents IK12 Change Measurement Documents IK13 Display Measurement Documents IK22 Measurement Documents List Editing - Create IK21 Measurement Documents List Editing - Create IK22 Measurement Documents List Editing - Create IK18 Measurement Documents List Editing - Change IK17 Measurement Documents List Editing - Display IK41 Measurement Documents List Editing - Display Archive IQ01 Create Serial Numbers IQ02 Change Serial numbers IQ04 Serial Numbers List Editing - Create IQ08 Serial Numbers List Editing - Change IQ09 Serial Numbers List Editing - Display IK01 Create Measurment Point IK02 Change Measurement Point Ik03 Display Measurement Point IK08 Measurement Point List Editing - Change Ik07 Measurement Point List Editing u2013 Display and a few PM related tables: TPST -- Functional Location - BOM Link STAS -- BOMs - Item Selection STKO -- BOM Header STPO -- BOM item STPU -- BOM Subitem STZU -- Permanent BOM data RESB - Reservation, Material number, Requirement date, Required Quantity, Quantity withdrawn, Work order number RSADD - Date created, User ID of person who created the reservation MAKT - Material Description AUFK - Work Order description AFIH - Revision (as a selection field) MBEW - Total valuated stock (SOH) USER_ADDR - The User ID first name & second name RKPF - Reservation Header information if required.
IP01 - maintenance plan
Plant maintenance (PM) IHPA Plant Maintenance: Partners OBJK Plant Maintenance Object List ILOA PM Object Location and Account Assignment AFIH Maintenance order header AFIH Maintenance Order Header AFKO Order header data PP orders AFPO Order item (not used much) AFRU Order completion confirmations AFVC Operation within an order AFVV Order position data CRCO Assignment of work center to cost center OBJK Plant Maintenance Object List CRHD Work Center Header PLAF Planned order HIKO Order master data history HIVG PM order history: operations Logical databases: CNJ AUFK Order master data AFKO Order header data PP orders AFPO Order item JSTO Status object information JEST Object status Logical databases: ODK 12.1 Routings/operations MAPL - Allocation of task lists to materials PLAS - Task list - selection of operations/activities PLFH - Task list - production resources/tools PLFL - Task list - sequences PLKO - Task list - header PLKZ - Task list: main header PLPH - Phases / suboperations PLPO - Task list operation / activity PLPR - Log collector for tasklists PLMZ - Allocation of BOM - items to operations 12.2 Bill of material STKO - BOM - header STPO - BOM - item STAS - BOMs - Item Selection STPN - BOMs - follow-up control STPU - BOM - sub-item STZU - Permanent BOM data PLMZ - Allocation of BOM - items to operations MAST - Material to BOM link KDST - Sales order to BOM link 12.3 PRTu2019s production orders AFFH - PRT assignment data for the work order CRVD_A - Link of PRT to Document DRAW - Document Info Record TDWA - Document Types TDWD - Data Carrier/Network Nodes TDWE - Data Carrier Type 12.4 Work center CRHH - Work center hierarchy CRHS - Hierarchy structure CRHD - Work center header CRTX - Text for the Work Center or Production Resource/Tool CRCO - Assignment of Work Center to Cost Center KAKO - Capacity Header Segment CRCA - Work Center Capacity Allocation TC24 - Person responsible for the work center 12.5 Classification CABS Result of the Statistical Analysis of Table AUSP CUFM Customizing: Class/Config: Screendesigner Form TCME Validity for Global Characteristics KLAH Class Header Data KLAT Classes: long texts KSML Characteristics of a Class AUSP Characteristic values SWOR Classification System: Catchwords KSSK Allocation Table: Object to Class TCLG Class groups TCLO Key Fields of Objects TCLS Classes: Organizational areas TCLST Classes: Org. Areas (Texts) TCLU Class Status COCC PP-PI attributes for characteristics COFV Process management - process instr. charact. in ctrl. recipe COME Process management - message characteristics CORE Process mgmt.- display characteristics of the eval. version PLFV PI Characteristics/Sub-Operation Parameter Values TCLA Class Types TCLAT Class Type Texts TCLT Classifiable Objects LTCLTT Classifiable Objects: Texts CABN Characteristic CAWN Characteristic values Logical databases: - Matchcodes: CLAS, MERK en KLSW 12.6 Equipment EQUI Equipment master data EQKT Equipment short texts EQUZ Equipment time segment EAPL Allocation of Task Lists to Pieces of Equipment EQUI Equipment master data JSTO Status object information JEST Object status TJ30 User status TJ30T Texts for user status TJ02 System status TJ02T Texts for system status 12.7 Functional Location IFLOT Functional Location (Table) IFLOTX Functional location: short texts IRLOTX Reference functional location: short texts TAPL Allocation of task lists to functional
Edited by: Sreenivasu on May 18, 2009 12:43 PM
Edited by: Sreenivasu on May 18, 2009 12:48 PM
Edited by: Sreenivasu on May 18, 2009 12:50 PM
Edited by: Sreenivasu on May 18, 2009 2:06 PM
Edited by: Sreenivasu on May 18, 2009 2:07 PM
Edited by: Sreenivasu on May 18, 2009 2:14 PM
Edited by: Sreenivasu on May 18, 2009 2:15 PM

Similar Messages

Field sales related tables and Transaction code

Dear SAPGurus,
I have been working with field sales activities in mySAP CRM..
Can I have the list of the tables and transaction code related to Field sales sales activies..
I am grateful for ur help....
I would like to appreciate u by rewarding the points
Thanks a lot

Hi Pratik Patel,
Thank u very much for sending the table names.They are all very useful unto me
Can I have the more table in this area
If u have the CRM Data model and its relationship...Pls share with me..
I appreciate ur help by rewarding the points
Regards,
CRM Consultant

Let me know what is new table and transaction code in ECC6?

Hi
As the above title, I want to know what is new table and transaction code, through from R/3 4.6c to ECC6.
Regards
Sang lim.

Hi Sang lim,
Apart from the tocdes listed above,
Transactions that changed from Release 4.6 C
Rel. Old TCode New TCode
46C ME51 ME51N
46C ME52 ME52N
46C ME53 ME53N
470 FNBD FNBT
470 ME54 ME54N
470 ME59 ME59N
46A MR01 MIRO
46A MR02 MRBR
46A MR08 MR8M
46A MR1G MIRO
46A MRHG MIRO
46A MRHR MIRO
46A MRRS MRRL
46B S_P99_41000327 S_ALR_87100205
46C MR03 MIR4
46C MR1B MIR6
46C MR2M MIR4
46C MR3M MIR4
46C MR41 MIR7
46C MR42 MIR4
46C MR43 MIR4
46C MR44 MIR4
46C MR5M MIR4
46C OAA2 AUFW
620 AFAB AFABN
620 AL01 RZ20
620 AL02 RZ20
620 AL03 RZ20
620 AR11 AR11N
620 AR29 AR29N
620 ASKB ASKBN
620 CA97 CA97N
620 DB02 DB02N
620 FM3S FMCIA
620 FM3U FMCIA
620 FMN3 FMN3N
620 FMN4 FMN4N
620 FMN5 FMN5N
620 O02E BMBC
620 OACR OAC0
620 RZ23 RZ23N
620 SCOM SCOT
620 SM22 SM21
620 SWID SWI2_DIAG
620 S_P9C_18000190 S_PL0_09000447
620 S_P9C_18000247 S_P6B_12000136
620 VOPA VOPAN
620 VOTX VOTXN
620 WE49 WE42
620 WE52 WE41
620 WE53 WE41
640 ABAW ABAWN
640 AL04 RZ20
640 AL19 OS07
640 COHVOMAVAILCHECK COMAC
640 COHVOMPI COHVPI
640 COHVOMPP COHV
640 KE1F KE1FN
640 KE29 KE29N
640 MKH1 MKH1N
640 MKH2 MKH2N
640 RZ02 RZ20
640 RZ06 RZ20
640 RZ08 RZ20
640 STAT STAD
640 STMP SLPP
640 VL22 VL22N
700 AL05 RZ20
700 AL16 RZ20
700 AL17 OS07
700 OVXA OVXAN
700 OVXG OVXGN
700 OVXJ OVXJN
700 OVXK OVXKN
700 OVXM OVXMN
700 OVX3 OVX3N
700 OVX6 OVX6N
700 OVX8 OVX8N
700 WLAM WLAMN
700 WLMM WLMMN
700 WLMV WLMVN
700 WLWB WLWBN
700 WPLG WPLGN
Regards,
Kiran

Master data tables and Transaction data Tables

Hello Gurus,
Please let me know how to know which table belongs to master data and which table belongs to transaction data.
for FICO module.
Does any one have specific material relating to master data table and transaction data tables.
Thanks
Edited by: Manu Rathore on Jan 18, 2012 4:38 AM

Hi Manu,
Find attached table relation diagram by Christopher Solomon. It is one of the very comprehensive chart on this topic.
deleted
Warm regards,
Murukan Arunachalam

Temp tables and transaction log

Hi All,
I am on SQL 2000.
When I am inserting(or updating or deleting) data to/from temp tables (i.e. # tables), is transaction log created for those DML operations?
The process is, we have a huge input dataset to process. So, we insert subset(s) of input data in temp table, treat that as our input set and do the processing in parts. Can I avoid transaction log generation for these intermediate steps?
Soon, we will be moving to 2008 R2. Are there any features in 2008, which can help me in avoiding this transaction logging?
Thanks in advance

Every DML operation is logged in the LOG file. Is that possible to insert the data in small chunks?
http://www.dfarber.com/computer-consulting-blog/2011/1/14/processing-hundreds-of-millions-records-got-much-easier.aspx
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Blog:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance

Set up table and transaction data delta load init

Dear experts,
I am following a document left by my predecessor on "post processing activities" for BI prod post go-live.
And for transaction data it says to :
1. execute init with data transfer infopack manually
2. execute delta update infopack manually
3. go to ECC : delete setup data (lbwg)
4. setup the tables for (OLIxxBW)
5. then finally activate Process chains.
Is this sequence correct?
Shouldn't I first delete the setup table, setup the tables and then execute the infopackages??
Regards,
Alice

Hi,
The sequence is correct ,and after this you need to run the job for the collective run in SAP ,which is based on your delta queue.
i.e if you choose direct delta it is not required ,but if you use 'queued delta' then you need to run the collective run to move the delta from the extraction queue to delta queue .This job should run before the delta load.
It is better to fill the set-up table during downtime .ie.no documents posted during the set-up table run. But if you dont have an option you can fill the set-up table during operation hours ,but need fo follow certain steps to get all the delta data. You may need to use 'Init without delta transfer' or early delta initialization in the infopackage .You need ODS as a data target to achieve this . Please search SDN ,you will get more information about this.
Thanks.

Table and transaction

Hi ,
I created one table and also creted a transaction code for that table where when we execute the transaction all the contents of the table are displayed in display mode.
Now i made the changes in the table (like field names , dataelements) and activated it.But these changes are not reflecting in the transaction.
Please tell me how to update transaction with the changes made in the table.

just check when u make transaction for table maintinance
in parameter value u pass
show 'X'
INSTEAD OF THIS PASS
UPDATE 'X'

Details on SAP Warehouse management? Basics, tables and transactions?

Hi
Soon i will be working on a SAP WM module as a abaper. I have worked on SD and MM modules but not worked on WM module.
Can anybody send me the links or guide me where i can find some basic information about SAP warehouse management?
I am looking for the following.
1). the complete process cycle in WM
2). basic tables used in WM
3). Basic transactions used in WM
thanks in advance.

check
https://forums.sdn.sap.com/click.jspa?searchID=12324135&messageID=4538695
https://forums.sdn.sap.com/click.jspa?searchID=12324135&messageID=2829284
Re: WM Flow
Regards
Kiran Sure

Cost center planning data table and transaction code to view

Hi,
I want to see the cost center planning document. In which transaction code, I can see this document.
In which table, cost center planning data is stored?
Regards,
VS ramaiah
Moderator: Please, search SDN

Hello,
I do not think that COEP contains the plan line items*. For plan line items it is COEJ. But as suggested by Christian the better option in case you want to create a report is you use COSS/COSP and COST. The latter is for activity type planning (KP26) and the other two are for cost planning (KP06).
The transactions to view the plan document is KABP and line items is KSBP.
* Christian, do correct me if I'm wrong. I was not able to see anything with value type 01 in COEP.
Kind Regards // Shaubhik

Customization tables and transactions

Hi everybody,
I have a very simple question:
I would like to know if every customization table is accessible through a transaction code.
If yes, then were can I find a table that contains the connection between customization table names and the transactions, which open them?
If no, then how can I access a customization table except for doing that through the SPRO?
Thanks,
Roy

Hi,
Check the table OBJSUB and
[How do I open a customization table for editing using my program?|Re: How do I open a customization table for editing using my program?;
Cheers,
Remi

Table AFRU, Transaction CO11N, confirmation not released?

Hi Gurus,
this question is regarding confirmation numbers (AFRU or other tables) and transaction CO11N.
can you help me in with problem (Test condition)?
Send notifications of not released orders.
my question is how? what table? field? transaction? anything. can someone explain me this? i made an FM that simulates CO11N and it is one of the test conditions.
Thanks

Hi,
Your question is not understood. Can you please explain a bit more. If you question is purely Functional, Please post the same in Functional Forum.

Relation between master and transaction data

Hi experts,
I have a basic question how the relation between masterdata and transction data is maintained in R/3. As I know first we extract master data and later transaction data in a typical R/3 based scenario.
1.How does BW knows that , the transaction data are related masterdata in the same sense as in R/3 ?
I am involved in an enhancement of R/3 extractor. I need to derive 3 more fields and map it to info objects in BW. Cld any one explain me ( with an example plz) how these alignments to be made. How can I establish relation b/w derived fields and transaction data during extractions ?
regs
D Bret

Hi Dave.
Let's see if I can get all of your questions answered. First, when Transactional Data is loaded, BW checks to see if a SID exists for each characterisatic field & value in the load. If one doesn't, it either creates a SID (Surregate ID) in the master data tables (default action) or the load fails (if the enforece referential intgegrity flag is set). It's better to load master data first in either case as it will improve the performance of the transactional load.
In terms of R/3, the data has similar relationships as in BW. There are master data tables and transactional data tables. The difference is that while R/3 uses ~1 master data table per field, BW uses more. Same thing for transactional data.
As for your enhancement, if everything you need for the derivation of the extra field is in R/3, then you can enhance the extractor in RSA6 and do the mapping in R/3. Once you replicate the DataSource to BW and reconnect the transformation & update rules, the load should work. If you can give a bit more information on what sort of enhancement you are attempting, I can give a better example.
Cheers,
Adam

Historical and transaction data in the same tables creates perf problems

Our Oracle based application is slow partly due to the fact that historical data are kept in the same table as transactional data. For example records about deceased patients, patients treated 5 years ago...etc, are kept in the one and only one patient table, which is needed to run the daily process of the hospital. So gradually all our major tables PATIENTS, CHARTS, NAMES, APPOINTMENTS have grown very large and since most of our SQL join all these tables at the same time, then all screens and reports run very slowly. I have introduced the idea that we should split all these tables in two: historical PATIENTS data, and CURRENT PATIENTS data...the same with all the others. A nice system would first search in the smaller transactional tables, which would run faster being smaller, and if no data found, then fallback to the historical tables. But this would require programming. From what I have read mateialized view could solve part of our problem. We could have views containing for example only one year worth of the data, and I guess any changes could be later replicated in the base table. What I dont know is what to do if we cannot find the patient in the matealized views ? Do I need to fallback to another SQL which will search in the initial base tables ? Anyway we can implement this without programming ? Tx.

Appointment table: 207,470
Visit table: 5,890,920
Patient table: 2,993,129
Chart table: 2,864,069
Patient names table: 3,938,118
SELECT
    APPOI_OR_VISIT,
    VISIT_SEQ,
    PAT_SEQ,
    INST_CODE,
    INST_CODE_DISPL,
    INST_DESC,
    CLINIC_CODE,
    CLINIC_CODE_DISPL,
    CLINIC_DESC,
    SPEC_CODE,
    SPEC_CODE_DISPL,
    SPEC_DESC,
    VISIT_DATE,
    VISIT_TIME,
    VISIT_TIME_ARRIVAL,
    APPTYPE_CODE,
    SESSION_DOM_MODE,
    PRESTYPE_CODE,
    PRESTYPE_DOM_TYPE,
    DIA_CODE,
    VISIT_TIME_START_RESP,
    VISIT_TIME_DISCHARGE,
    APPOI_NB_DURATION,
    VISIT_TX_REASON,
    VISIT_TX_COMMENT,
    EXTDOC_CODE,
    VISIT_PN_REFPHYS_NAME,
    PATYPE_CODE,
    PAYRESP_CODE,
    VISIT_IND_GROUP,
    VISIT_PCODE,
    VISIT_IND_COMPLETE,
    VISIT_IND_ADMISSION,
    VISIT_IND_CONFIDENTIALITY,
    VISIT_DATE_ACCIDENT,
    APPOI_SEQ,
    BILLING_CODE,
    VISIT_TX_DIAGNOSIS,
    CST_CODE_1,
    CST_CODE_2,
    CST_CODE_3,
    APPOI_DH_CRE,
    APPOI_CODE_CRE_USER,
    APPOI_DH_MOD,
    APPOI_CODE_MOD_USER,
    VISIT_CODE_CRE_USER,
    VISIT_DH_CRE,
    VISIT_UPDATED_COUNT,
    VISIT_CODE_MOD_USER,
    VISIT_DH_MOD,
    APPOI_PAYRESP_CODE,
    APPOI_DT_ACCIDENT,
    PATIENT_LAST_NAME,
    PATIENT_FIRST_NAME,
    PATIENT_CONFIDENTIALITY,
    PATIENT_CHART_EXT,
    TO_NUMBER(SUBSTR(PATIENT_CHART_EXT, 1, INSTR(PATIENT_CHART_EXT, '|')-1)) AS PATIENT_CHART_NO,
    PAT_IND_SPECIAL_RISK
FROM
    SELECT
        'VISIT'              AS APPOI_OR_VISIT,
        VISIT.VISIT_SEQ,
        VISIT.PAT_SEQ,
        INSTITUTION.INST_CODE,
        INSTITUTION.INST_CODE_DISPL,
        INSTITUTION.INST_DESC,
        CLINIC.CLINIC_CODE,
        CLINIC.CLINIC_CODE_DISPL,
        CLINIC.CLINIC_DESC,
        SPECIALTY.SPEC_CODE,
        SPECIALTY.SPEC_CODE_DISPL,
        SPECIALTY.SPEC_DESC,
        VISIT.VISIT_DATE,
        VISIT.VISIT_TIME,
        VISIT.VISIT_TIME_ARRIVAL,
        VISIT.APPTYPE_CODE,
        VISIT.SESSION_DOM_MODE,
        VISIT.PRESTYPE_CODE,
        VISIT.PRESTYPE_DOM_TYPE,
        VISIT.DIA_CODE,
        VISIT.VISIT_TIME_START_RESP,
        VISIT.VISIT_TIME_DISCHARGE,
        VISIT.APPOI_NB_DURATION,
        VISIT.VISIT_TX_REASON,
        VISIT.VISIT_TX_COMMENT,
        VISIT.EXTDOC_CODE,
        VISIT.VISIT_PN_REFPHYS_NAME,
        VISIT.PATYPE_CODE,
        VISIT.PAYRESP_CODE,
        VISIT.VISIT_IND_GROUP,
        VISIT.VISIT_PCODE,
        VISIT.VISIT_IND_COMPLETE,
        VISIT.VISIT_IND_ADMISSION,
        VISIT.VISIT_IND_CONFIDENTIALITY,
        VISIT.VISIT_DATE_ACCIDENT,
        VISIT.APPOI_SEQ,
        VISIT.BILLING_CODE,
        VISIT.VISIT_TX_DIAGNOSIS,
        VISIT.CST_CODE_1,
        VISIT.CST_CODE_2,
        VISIT.CST_CODE_3,
        VISIT.APPOI_DH_CRE,
        VISIT.APPOI_CODE_CRE_USER,
        VISIT.APPOI_DH_MOD,
        VISIT.APPOI_CODE_MOD_USER,
        VISIT.VISIT_CODE_CRE_USER,
        VISIT.VISIT_DH_CRE,
        VISIT.VISIT_UPDATED_COUNT,
        VISIT.VISIT_CODE_MOD_USER,
        VISIT.VISIT_DH_MOD,
        NULL AS APPOI_PAYRESP_CODE,
        TO_DATE(NULL) AS APPOI_DT_ACCIDENT,
        NAME.NAM_PN_NAM AS PATIENT_LAST_NAME,
        NAME.NAM_PN_FNAM AS PATIENT_FIRST_NAME,
        CONFIDENTIALITY.CONF_DESC AS PATIENT_CONFIDENTIALITY,
        PI_SECURITY.F_GET_CHART_NUMBER_SCAN_CODE(VISIT.PAT_SEQ, 103 /*:pChartInstitutionID*/, 0) AS PATIENT_CHART_EXT,
        PATIENT.PAT_IND_SPECIAL_RISK
    FROM
               AS_T_VISITS        VISIT,
               CT_R_INSTITUTIONS INSTITUTION,
               AS_T_CLINICS       CLINIC,
               CT_R_SPECIALITIES SPECIALTY,
               PI_T_NAMES         NAME,
               PI_T_PATIENTS      PATIENT,
               PI_R_CONF_LEVELS   CONFIDENTIALITY
    WHERE
        VISIT_DATE >= TO_DATE('2004-04-01', 'YYYY-MM-DD') /*:P_VISIT_DATE_FROM*/ AND
        VISIT_DATE <= TO_DATE('2004-04-02', 'YYYY-MM-DD') /*::P_VISIT_DATE_TO*/ AND
        CLINIC.CLINIC_CODE = VISIT.CLINIC_CODE AND
        SPECIALTY.SPEC_CODE = CLINIC.SPEC_CODE AND
        INSTITUTION.INST_CODE(+) = VISIT.INST_CODE AND
        NAME.PAT_SEQ = VISIT.PAT_SEQ AND
        NAME.NAMTYP_CODE = 1 AND
        PATIENT.PAT_SEQ = VISIT.PAT_SEQ AND
        CONFIDENTIALITY.CONF_CODE (+) = PATIENT.CONF_CODE
    UNION
    SELECT
        'APPOI'                                                                                                                                                                                                        AS APPOI_OR_VISIT,
        0                                                                                                                                                                                                                            AS VISIT_SEQ,
        NVL(APPOINTMENT_GROUP.PAT_SEQ, APPOINTMENT.PAT_SEQ) AS PAT_SEQ,
        INSTITUTION.INST_CODE,
        INSTITUTION.INST_CODE_DISPL,
        INSTITUTION.INST_DESC,
        CLINIC.CLINIC_CODE,
        CLINIC.CLINIC_CODE_DISPL,
        CLINIC.CLINIC_DESC,
        SPECIALTY.SPEC_CODE,
        SPECIALTY.SPEC_CODE_DISPL,
        SPECIALTY.SPEC_DESC,
        APPOINTMENT.SESSION_DATE                                                                                                                                                                AS VISIT_DATE,
        APPOINTMENT.APPOI_TIME                                                                                                                                                                     AS VISIT_TIME,
        ''                                                                                                                                                                                                                  AS VISIT_TIME_ARRIVAL,
        APPOINTMENT.APPTYPE_CODE,
        APPOINTMENT.SESSION_DOM_MODE,
        0                                                                                                                                                                                                                            AS PRESTYPE_CODE,
        ''                                                                                                                                                                                                                  AS PRESTYPE_DOM_TYPE,
        0                                                                                                                                                                                                                            AS DIA_CODE,
        ''                                                                                                                                                                                                                  AS VISIT_TIME_START_RESP,
        ''                                                                                                                                                                                                                  AS VISIT_TIME_DISCHARGE,
        APPOINTMENT.APPOI_NB_DURATION,
        APPOINTMENT.APPOI_TX_REASON                                                                                                                                                           AS VISIT_TX_REASON,
        APPOINTMENT.APPOI_TX_COMMENT                                                                                                                                                      AS VISIT_TX_COMMENT,
        APPOINTMENT.EXTDOC_CODE,
        APPOINTMENT.APPOI_PN_REFPHYS_NAME                                                                                                                                            AS VISIT_PN_REFPHYS_NAME,
        APPOINTMENT_TYPE.PATYPE_CODE AS PATYPE_CODE,
        0                                                                                                                                                                                                                            AS PAYRESP_CODE,
        DECODE(APPOINTMENT_GROUP.PAT_SEQ,NULL,0,1)                                                                                                                   AS VISIT_IND_GROUP,
        ''                                                                                                                                                                                                                  AS VISIT_PCODE,
        0                                                                                                                                                                                                                            AS VISIT_IND_COMPLETE,
        0                                                                                                                                                                                                                            AS VISIT_IND_ADMISSION,
        APPOINTMENT.APPOI_IND_CONFIDENTIALITY                                                                                                                                  AS VISIT_IND_CONFIDENTIALITY,
        TO_DATE(NULL)                                                                                                                                                                                          AS VISIT_DATE_ACCIDENT,
        APPOINTMENT.APPOI_SEQ,
        0                                                                                                                                                                                                                            AS BILLING_CODE,
        ''                                                                                                                                                                                                                  AS VISIT_TX_DIAGNOSIS,
        0                                                                                                                                                                                                                            AS CST_CODE_1,
        0                                                                                                                                                                                                                            AS CST_CODE_2,
        0                                                                                                                                                                                                                            AS CST_CODE_3,
        APPOINTMENT.APPOI_DH_CRE                                                                                                                                                                AS APPOI_DH_CRE,
        APPOINTMENT.APPOI_CODE_CRE_USER                                                                                                                                                 AS APPOI_CODE_CRE_USER,
        APPOINTMENT.APPOI_DH_MOD                                                                                                                                                                AS APPOI_DH_MOD,
        APPOINTMENT.APPOI_CODE_MOD_USER                                                                                                                                                 AS APPOI_CODE_MOD_USER,
        ''                                                                                                                                                                                                                  AS VISIT_CODE_CRE_USER,
        SYSDATE                                                                                                                                                                                                             AS VISIT_DH_CRE,
        0                                                                                                                                                                                                                            AS VISIT_UPDATED_COUNT,
        ''                                                                                                                                                                                                                  AS VISIT_CODE_MOD_USER,
        SYSDATE                                                                                                                                                                                                             AS VISIT_DH_MOD,
        PAYRESP_CODE                                                                             AS APPOI_PAYRESP_CODE,
        APPOI_DT_ACCIDENT,
        NAME.NAM_PN_NAM AS PATIENT_LAST_NAME,
        NAME.NAM_PN_FNAM AS PATIENT_FIRST_NAME,
        CONFIDENTIALITY.CONF_DESC AS PATIENT_CONFIDENTIALITY,
                                    PI_SECURITY.F_GET_CHART_NUMBER_SCAN_CODE(APPOINTMENT.PAT_SEQ, 103 /*:pChartInstitutionID*/, 0) AS PATIENT_CHART_EXT,
        PATIENT.PAT_IND_SPECIAL_RISK
    FROM
               AS_T_APPOINTMENTS       APPOINTMENT,
               AS_R_APPOINTMENT_TYPES APPOINTMENT_TYPE,
               AS_T_CLINICS            CLINIC,
               CT_R_SPECIALITIES       SPECIALTY,
               CT_R_INSTITUTIONS       INSTITUTION,
               AS_T_APPOINTMENT_GROUPS APPOINTMENT_GROUP,
               PI_T_PATIENTS           PATIENT,
               PI_R_CONF_LEVELS        CONFIDENTIALITY,
               PI_T_NAMES              NAME,
               AS_T_APPOINTMENT_SEQ_MAPPING SEQMAP
    WHERE
        SESSION_DATE >= TO_DATE('2004-04-01', 'YYYY-MM-DD') /*:P_VISIT_DATE_FROM*/ AND
        SESSION_DATE <= TO_DATE('2004-04-02', 'YYYY-MM-DD') /*::P_VISIT_DATE_TO*/ AND
        APPOINTMENT.APPOI_DOM_TYPE IN('A','AR') AND
        CLINIC.CLINIC_CODE = APPOINTMENT.CLINIC_CODE AND
        SPECIALTY.SPEC_CODE = CLINIC.SPEC_CODE AND
        INSTITUTION.INST_CODE(+) = APPOINTMENT.INST_CODE AND
        APPOINTMENT_GROUP.APPOI_SEQ (+) = APPOINTMENT.APPOI_SEQ AND
        APPOINTMENT_TYPE.APPTYPE_CODE (+) = APPOINTMENT.APPTYPE_CODE AND
        NAME.PAT_SEQ = NVL(APPOINTMENT.PAT_SEQ, APPOINTMENT_GROUP.PAT_SEQ) AND
        NAME.NAMTYP_CODE = 1 AND
        PATIENT.PAT_SEQ = NVL(APPOINTMENT.PAT_SEQ, APPOINTMENT_GROUP.PAT_SEQ) AND
        CONFIDENTIALITY.CONF_CODE (+) = PATIENT.CONF_CODE AND
        SEQMAP.APPOI_SEQ (+) = APPOINTMENT.APPOI_SEQ AND
        SEQMAP.APPOI_SEQ IS NULL
ORDER BY
     VISIT_DATE, VISIT_TIME, PATIENT_CHART_NO

Transaction DB02 = Missing Tables and Indexes shows under Secondary indexes from package $tmp

Hi SAP Gurus,
I noticed on our SAP business warehouse (BW) system (NetWeaver 7.0 based on AIX/Oracle 11g) in transaction DB02 => Diagnostics => Missing Tables and Indexes under Secondary indexes, 26 indexes, in package $tmp:
The indexes are defined, but they don't have been created on the database.
When I try to create them via the database tool, I am getting the warning:
Does the warning raise up, because they where defined in the $tmp package?
I was looking in SAP notes for a solution for this "warning" concerning the /BIC/F-Indexes but I didn't found yet anything helpful ...
Thanks for your help and ideas ...
Best regards
Carlos

Hi Carlos,
These are secondary indexes created during process chains in BI to improvise performance.
You may refer below SCN blogs on creation of these indices in BI.
Secondary Index - Improving DSO insert/read performance
How to Create Secondary Index on DSO in SAP BW
Hope this helps.
Regards,
Deepak Kori

Z programs, Z tables, and Z transactions

Good day everyone,
If I want to see the code behind a Z program, how do I look that up?
Also, is there code behind Z tables and Z transactions? If so, how do I look that up as well?
Thanks,

Are you really asking how to see program code?
Please search for available information before asking such extremely basic questions.
Thread locked.
Thomas

PM Tables and Transaction

Similar Messages

Maybe you are looking for