MD04 Transaction Data Table

Hi,
I want to know the table name for MD04 transaction data. in that transaction i am giving Material, Plant. its showing MRP values and stock. i need to know where it is storing?
points will be rewarded for helpful answers.
Regards,
Balu

Hi,
Just Use:
    CALL FUNCTION 'MD_STOCK_REQUIREMENTS_LIST_API'
    EXPORTING
PLSCN = "Planning Scenario of Long-Term Planning
    matnr = <t_marc>-matnr "Material Number
    werks = <t_marc>-werks "Plant
    inper = 'M'   "For Months
   ergbz = s_ergbz-low
BERID = "MRP Area
IMPORTING
E_MT61D =
E_MDKP =
E_CM61M =
E_MDSTA =
    TABLES
   MDPSX = t_mdps
   mdezx = t_mdez
    mdsux = t_mdsu  "Summary table
    EXCEPTIONS
    material_plant_not_found = 1
    plant_not_found = 2
    OTHERS = 3.
Please it is exactly replica of MD04, so whatever is possible in MD04 e.g. setting the filter, everything is possible in this FM as it has got all the required parameters. In the above example I am retrieving the 'Summary' data monthwise.
I hope this helps,
Regards
Raju Chitale

Similar Messages

  • Change Profit centers in all transactional data tables

    Hello Experts,
    I have been assigned to change Profit center MASKTOOLS to BRION in all transaction data tables.
    Is there any standard SAP programs/reports that will help me do this?
    How do I identify all tables were Profit center is stored?
    Bearing in mind if I make changes directly in tables (example via Abap programs) BW will not recognise any changed documents and therefore not update BW accordingly.
    Regards in advance Steve

    Thanks Karthik T,
    What about Internal orders, Sales orders, Service orders, Production orders, PA segments etc etc. etc..
    I also have to think about orders with settlement rules which hold both profit center and profitablility segments which also hold profit centers.
    I am still hoping there is SAP standard reports that can help identify and change
    Steve D

  • 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

  • CCA Transaction Data Table

    Hi,
    What is the R/3 table for Cost center transaction data?
    Thanks

    Hi
    The following are the few tables for cost center accounting
    COKA CO Object- Control Data for Cost Elements
    COSP CO Object- Cost Totals for External Postings
    COSS CO Object- Cost Totals for Internal Postings
    CRCO Assignment of Work Center to Cost Center
    CSKA Cost Elements (Data Dependent on Chart of Accounts)
    CSKB Cost Elements (Data Dependent on Controlling Area)
    CSLA Activity master
    For more tables:
    http://www.erpgenie.com/abap/tables_fi.htm
    Regards
    srikanth

  • How to View master data & Trasaction data tables for Puchasing Cube

    Hi BW masters,
    How should I check which tables (Master data tables and Transaction data tables) are involved with Business Content Cube(Purchasing data 0PUR_C01). I would like to know this information in order to go to that table and browse the data in that table. Where should we go and check this out.
    I will reward the points for the good answers.:-)
    Thanks
    Syed.

    hi Syed,
    to view tables' content you can use SE16,
    you can try infocube name, dimension tables of cube are store in *d[infocube name]1 to F, fact tables are f[infocube name] and e[infocube name]-compress,
    infocube data are stored in star schema, you can use LISTCUBE to view the content (to see the structure/tables in cube, use LISTSCHEMA),
    master data (not time-dependent) are stored in text table t[infoobject name], attribute - p[infoobject name] and hierarchy - h[infoobject name],
    take a look bw multidimensional data modeling for detail
    http://help.sap.com/bp_biv235/BI_EN/documentation/Multi-dimensional_modeling_EN.doc
    hope this helps.

  • 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

  • Transaction data can be loaded into the Fact table without loading the

    Transaction data can be loaded into the Fact table without loading the corresponding master data (Example : Sales analysis transaction data can be loaded without populating any of its  dimension’s master data)
    a.     True
    b.     False

    Hi Kutti,
    True - You need to select the option in the infopackage - alwyas load even if no master data exists.
    Bye
    Dinesh

  • While loading transaction data into cube what are the tables generats

    Hi,
    while loading transaction data into cube what are the tables normally generats.

    Hi,
    Normally datas will be loading to 'F'- Fact tables (/BIC/F****) *** - cube name..
    When you do compress the request the data will be moved into E tables.
    Regards,
    Siva.

  • 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

  • TABLES FOR MASTER & TRANSACTIONAL DATA

    Hi all ,
    can some body help me with TABLES FOR MASTER & TRANSACTIONAL DATA
    DP,SNP,PP/DP.
    Thanks

    Hi,
    You can find out it as per your requirement.
    Use transaction SE80 - ABAP workbench  -->
    select Repository Information system  -->
    Select ABAP Dictionary  --> Data base table -->
    In the right hand side window you will get screen in that give details as below
    Standard selection screen
    Table name : enter *
    In the Application Component:
    You will get Tree structure to Select Application Componenet
    in that expand the node of SCM --> SCM APO --> SCM-APO-MD for Master Data
    Here you will get application  -- Double click on the required Application
    e.g. Duble Click on SCM-APO-MD-PR for Product
    Here you will get list of table related to application componenet Product
    <b>/SAPAPO/MATKEY                 Product</b>
    Some of the Master Data Tables:
    /SAPAPO/APNTYPE                APN Type
    /SAPAPO/APNTYPET               Alternative Product Number Type
    /SAPAPO/APO01                  APO Planning Version
    /SAPAPO/APO01DEL               Deletion Log File Versions
    /SAPAPO/APPLOCS                Location Master: Relevant Location Types for Application
    /SAPAPO/APPLS                  Application Types : SAP Application Types
    /SAPAPO/CD_LOC                 Customizing Change Documents Location
    /SAPAPO/CD_PPRFL               Customizing: Change Documents: Product Profiles
    /SAPAPO/CD_PRDHD               Customizing: Change Documents: Product
    /SAPAPO/CD_PRDLC               Customizing: Change Documents: Location Product
    /SAPAPO/CD_PRDLW               Customizing: Change Documents: Storage Type Product
    /SAPAPO/CD_PRDWH               Customizing: Change Documents: Storage Type Product
    /SAPAPO/CONSPROF               Model Consistency Check: Check Profile
    /SAPAPO/CONSPROT               Model Consistency Check: Check Profile Descriptions
    /SAPAPO/CUSTCHK                Model Consistency Check: User-Specific Checks
    /SAPAPO/CUSTCHKT               Model Consistency Check: Descriptions of User-Spec. Checks
    /SAPAPO/GRPTYPE                Product Group Types
    /SAPAPO/GRPTYPET               Description of Product Grouping
    /SAPAPO/LOC                    Locations
    /SAPAPO/LOC_SUB                Mapping Table for Sublocations
    /SAPAPO/LOCCOMP                Table Obsolete Since SCM Release 4.1
    /SAPAPO/LOCMAP                 Mapping Table for Locations
    /SAPAPO/LOCMOT                 Location: Means-of-Transport-Dependent Attributes
    /SAPAPO/LOCPROF                Version-Dependent Location Profile for Penalty Determinati
    /SAPAPO/LOCT                   Locations Short Text
    /SAPAPO/LOCVER                 Location: Version-Dependent Fields
    /SAPAPO/LTTYPE                 Location Resources
    /SAPAPO/LTVER                  Location Resources: Version-Dependent Fields
    /SAPAPO/MARM                   Units of Measure
    /SAPAPO/MATAPN                 Alternative Product Number
    /SAPAPO/MATBOD                 Product BOD Assignment
    Hope this information will be helpful for you work on and find out Important tables for your own BP

  • Table name for the transaction data

    Hello Gurus,
        what is the table name for the transaction data which we have created through t.code PRO5. we are generating report for the total kms per vehicle type for a employee. these data in which tables can i get? the data related to trips ? 
    thanks in advance
    regds
    ramachandra

    Hi,
    Pl use RPR_TRIP_HEADER_DATA programme for getting general trip data, which will have details about number of KM travelled by employee for each trip, amount to reimbursed to the employee etc.
    Thanks,
    Nandagopal C

  • Why APO transaction data is not stored in tables

    Hi All,
    Why APO transaction data is not stored in tables.
    can u explain me.
    Babu

    Good question Babu,
    There indeed are tables for master data in APO database whereas the transaction data (qty, amount, dates and document numbers) are stored in a denormalized data base called livecache. But the master data too is identified with GUID's.. a cryptic and unique number given to e.g. a location, prodcuct, t/lane, customer and documents. This is because of speed of access if e.g. an external system is to fetch an information from APO using a unique session ID, instead of making a sequential read in APO tables, it read the live cache by called the GUID's that the calling characterics of the event. If one or more ECC system or an external execution system is connected to APO and one of the system collapses and rebuild again or if a system is assigned to a new business system group etc.. then its likely that systems can be out of sync and its where the live cache syncs up the data with APO tables again. If you still want to see tables in human readable format.. there are views available e..g the tables for locations LOCID and table for products MATLOC would take only GUID as inputs but the view V_MATLOC will show you the materials and locations by the numbers you know.
    Hope I was able to explain. But yes the why part is still something of a mystery to me.. becasue with transparent tables it is easier to create local reports in APO and thats what probably SAP doesnt want. SAP can answer best as to what were the initial user and commercial considerations when developing APO
    Regards,
    Loknath

  • Unexpected transaction data in fact table

    Hi,
    I  have created customized table having field
    SWISSEMPID   SWEMPNAME   SWADDRESS   SWDESIGNATION
    SWHIREDATE   SUPERVISOR    SWISSCOMP    ETHNICITY     LANGUAGE       CURRENCY
    On the basis of table , I have created generic data source for text ( empname ) and attr ( empid)
    dtp excetuded successfully
    but for transaction data , in extract structure I have taken empid and empname for connecting dimension
    table to fact table , compensation also selected ( transaction data)
    after exectuing dtp i am getting 426000 value , it is repeated for each record
    which does not exist in table
    Regards,
    Vivek
    Edited by: Vivek Srivastava on Jan 13, 2010 9:07 AM

    You need to explain your requirement a bit more. Why you want to add type or rejection reason in fact table.
    In general you should avoid adding textual data in fact.
    Fact tables are only supposed to store keys and measures. It can hold textual data in case of degenerate dimension ( i.e if the number of records are same in dimension as well as fact ).
    Type or Rejection reason are going to have much less records. You can create a new dimension for them having probably 20 or 30 records.
    Disadvantages of adding textual data in fact is, once the fact has millions of records the fact table updates are going to take huge time and also your reports will take long time.
    If you have a rejection reason dimension with some 20 records, you can use rejection reason in prompts.
    But if the same rejection reason is coming from fact table your prompts performance is going to be very slow since it has to fetch 20 distinct records from millions of records.
    Consider these before adding textual data in facts.
    Thanks
    Edited by: Maqsood Hussain on Dec 5, 2012 9:40 PM

  • 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.

  • Master data tables with unwanted records from transaction data upload

    Hi Friends,
      I have a master data table for infoobject 'C' with compounding characteristics 'A' & 'B'.  I upload this master data with values given below:
        <i><u> A,              B,              C,           Short text,                        Long text</u></i>
           <b>  <b>P,          10,           BBB,         Apple,                              Big Apples
             Q,             20 ,           XYZ  ,       Tomatoes    ,                    Red Tomatoes</b></b>
      When I load data into ODS from a source system, I may not necessarily have data for all these 3 fields in these transaction record.  Example:
      <i><u>     A,                B,             C,             D,            E</u></i>    
         <b> P                -1            FFF</b>          20           30            
         <b> Q                10           GGG        </b> 10           40
       The problem is when I upload the above transaction data, it populates the <b>master data table</b> too with these two new records <b>1 -1 FFF</b> and  <b>2 10 GGG</b>, which I would like to avoid.
       Is there any way?
       Will assign full points to anyone who helps me here.
       Thanks,
       JB

    Hi JB,
    If you want to load transactional data and still want to prevent the population of the master data table, I don't think it is possible, as it is goes aginst the data consistency in the warehouse.
    However, if you can afford not to load transactional data for such cases, you can activate referential integrity check for the infoobject C. Then neither transactional data nor masterdata enter the datawarehouse until you maintain masterdata yourself for the infoobject C.
    hope this helps.

Maybe you are looking for