DataSource is "NOT EXECUTABLE" in Production

Hi,
We are working on BI 7.0 and trying to move the objects of my module in to Production.
One Generic DataSource(Master Data Attribute) has been first transported in to Production R/3 , from there I replicated this DataSource in Production BI...and symultaneously all the related objects related to this DataSources were also transported from Dev BI to Production BI.
in RSA6, I checked Object Directory entry for that particular DataSource...It's perfectly locked under particular Package and in my own request.
Still, when I replicated it from Production R/3 to Production BI, it's not properly activated...means....the version is showing as "ACTIVE", But Active Version as "NOT EXECUTABLE"(Edited Version) .... and the datasource is not highlighted with green color....
Can somebody help me in finding what could be the error and appropriate solutions....
Thanks guys......Intros

Hi,
Are you using 3.x data source or 7.0 data source.
In case you are using 3.x data source make sure you have replicated the data source as a 3.x data source in to BW.
Please use function module RSAOS_DATASOURCE_ACTIVATE
and check the error message you are getting.
Regards,
Nitin

Similar Messages

Query not executing on production but on dev server

Hi,
I have few queries which are running in less then a second in development server but couldn't get executed on production server in three hours. Production box is much heavier then the development server. I have verified the init.ora parameters. both the boxes have same parameters and same data. How should I start the investigation on the same problem?
Need urgent help.
Thanks is Advance.
Thanks, Dewan

user463820 wrote:
Production box is much heavier then the development server. I have verified the init.ora parameters. both the boxes have same parameters and same data.Which might be a contributing factor to:
I have few queries which are running in less then a second in development server but couldn't get executed on production server in three hours. Do you have QA environment with production-like data? In any case, make sure statistics is collected and is up to date. Get explain plan for queries in question. See if execution plan isn't optimal.
SY.

"vi is not executable" built app - product feature request

OK, here's what I want for the next version of LabVIEW. Forget a real implementation of OO. Forget about making XControls so that you don't need a PhD to program them. Forget about a real polymorphic control (down all you who say "variant!"). Here's what I want for the next feature of LabVIEW.
I want the run-time engine to give me a better idea of why a built application won't run. The generic "This VI is not executable. The full development version of LabVIEW is required to fix the errors..." is meaningless. If the VI works just fine in the development environment, and it builds without errors, why does it not run? If there's so many reasons, how is one supposed to track it down?
I've been using LabVIEW since version 2 on a Mac, so I like to think that I know what I'm doing with it. Yet, whenever I run into this I feel helpless because I have NO information! This is frustrating beyond my ability to put into words. And please don't tell me to look at this article or this other article in your KnowledgeBase. Been there, done that. In one situation I tracked the problem down to a VI. Couldn't find ANYTHING wrong with it. So, I created a new VI, copied the block diagram over, and saved the new VI over it. Rebuilt the app, and presto, the app worked. Do you know how long it took me to track it down to that VI? About half a day. Was there ANYTHING that gave me a clue as to the problem? Can you say rhetorical question?
I'm posting this here in the hopes that enough people get my grief, and head over to the Product Suggestion Form to hopefully make this pipe dream a reality. Power to the people!
Now, back to figuring out why my latest built application won't run. Guess what I'll be doing for the next half-day or so.

smercurio, i can't help you, but i'm with you, maybe that makes you feel better.
i upgraded a LV-app i created originally with 7.1 (this was the best LV ever, in my opinion) to 8.20. i was forced to do that because of the 64bit feature of ms tickers. it took me about 4hrs to create a project to generate an executable, after several LV-crashes during editing. finally i managed to get the project working (compiling took about 10 mins, with the 7.1 app builder about 1 min!! same code!!!), and then there was this error message: "error blabla in VI blubblub", and the VI was part of the vi.lib! so what to do?
KB: no answer!
discussion forum: no hits!
i found a post in the forum about another error code, but the same scenario. workaround was to disable the "remove as much as possible" option in the advanced project settings.
result: size of executable increased about 100%, while execution speed decreased about 50% compared to the 7.1 version, though all of the "code enhancement features" of 8.20.
now i'm thinking of switching back to 7.1 and to workaround the limits of long execution times with 32bit tickers.
i'm a big fan of LV, and i'm dealing with it since 1998, not for fun, but as a professional programmer. but 8.2 is a real step backwards in quality in my opinion. i think this has to be said to make 9.0 better!
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

Why This Report Not Working in Production Server But in Development Server

I just need your help in solving one issue. There is one report which is working fine in development server but it is not getting executed in production server.
Although the code is same in both the server. Could you please guide me in locating the problem. I am attaching that report with this mail. Please do the needful help.
TABLES : a363,
         mara,
         marc,
         makt,
         ekko,
         ekpo,
         mkpf,
         mseg,
         konp,
         konh.
SELECTION-SCREEN
SELECTION-SCREEN   :   BEGIN OF BLOCK cst WITH FRAME TITLE text-001.
SELECT-OPTIONS :   s_matnr FOR mara-matnr,                            "Material Number
                   s_lifnr FOR ekko-lifnr,                            "Account Number of the Vendor
                   s_bedat FOR ekko-bedat,                            "Purchasing Document Date
                   s_kschl FOR konh-kschl OBLIGATORY NO INTERVALS,    "Condition type
                   s_bwart FOR mseg-bwart OBLIGATORY NO INTERVALS.    "Movement Type (Inventory Management)
PARAMETERS     :   p_werks LIKE marc-werks OBLIGATORY.                "Plant
SELECTION-SCREEN   :   END OF BLOCK cst.
INCLUDES
INCLUDE zalv_data.
DATA - INTERNAL TABLES AND FIELD LISTS
DATA : BEGIN    OF     a363_itab OCCURS 0,
        matnr    LIKE   a363-matnr,                    "Material Number
        lifnr    LIKE   a363-lifnr,                    "Account Number of the Vendor
        werks    LIKE   a363-werks,                    "Plant
        kschl    LIKE   a363-kschl,                    "Condition type
        knumh    LIKE   a363-knumh,                    "Condition record number
        kbetr    LIKE   konp-kbetr,                    "Rate (condition amount or percentage) where no scale exists
        END      OF     a363_itab.
DATA : BEGIN    OF     konp_itab OCCURS 0,
        knumh    LIKE   a363-knumh,                    "Condition record number
        kbetr    LIKE   konp-kbetr,                    "Rate (condition amount or percentage) where no scale exists
        lifnr    LIKE   a363-lifnr,                    "Account Number of the Vendor
        END      OF     konp_itab.
DATA : BEGIN    OF     ekko_itab OCCURS 0,
        ebeln    LIKE   ekko-ebeln,                    "Purchasing Document Number
        lifnr    LIKE   ekko-lifnr,                    "Account Number of the Vendor
        bedat    LIKE   ekko-bedat,                    "Purchasing Document Date
        END      OF     ekko_itab.
DATA : BEGIN    OF     ekpo_itab OCCURS 0,
        ebeln    LIKE   ekpo-ebeln,                    "Purchasing Document Number
        ebelp    LIKE   ekpo-ebelp,                    "Item Number of Purchasing Document
        matnr    LIKE   ekpo-matnr,                    "Material Number
        werks    LIKE   ekpo-werks,                    "Plant
        menge    LIKE   ekpo-menge,                    "Purchase order quantity
        END      OF     ekpo_itab.
DATA : BEGIN    OF     v_po_det OCCURS 0,            "VENDOR + PLANT + PO DEATILS
        lifnr    LIKE   ekko-lifnr,                    "Account Number of the Vendor
        ebeln    LIKE   ekko-ebeln,                    "Purchasing Document Number
        ebelp    LIKE   ekpo-ebelp,                    "Item Number of Purchasing Document
        bedat    LIKE   ekko-bedat,                    "Purchasing Document Date
        matnr    LIKE   ekpo-matnr,                    "Material Number
        werks    LIKE   ekpo-werks,                    "Plant
        menge    LIKE   ekpo-menge,                    "Purchase order quantity
        kbetr    LIKE   konp-kbetr,                    "Rate (condition amount or percentage) where no scale exists
        END      OF     v_po_det.
DATA : BEGIN    OF     mseg_itab OCCURS 0,
        mblnr    LIKE   mseg-mblnr,                    "Number of Material Document
        ebeln    LIKE   mseg-ebeln,                    "Purchasing Document Number
        ebelp    LIKE   mseg-ebelp,                    "Item Number of Purchasing Document
        matnr    LIKE   mseg-matnr,                    "Material Number
        lifnr    LIKE   mseg-lifnr,                    "Account Number of the Vendor
        werks    LIKE   mseg-werks,                    "Plant
        menge    LIKE   mseg-menge,                    "Quantity
        dmbtr    LIKE   mseg-dmbtr,                    "Amount in local currency
        bwart    LIKE   mseg-bwart,                    "Movement Type (Inventory Management)
        END      OF     mseg_itab.
DATA : BEGIN    OF     mkpf_itab OCCURS 0,
        mblnr    LIKE   mkpf-mblnr,                    "Number of Material Document
        bldat    LIKE   mkpf-bldat,                    "Document Date in Document
        END      OF     mkpf_itab.
DATA : BEGIN    OF     zeou_pcrdtl_itab OCCURS 0,
        matnr    LIKE   zeou_pcrdtl-matnr,             "Material Number
        lifnr    LIKE   zeou_pcrdtl-lifnr,             "Account Number of the Vendor
        mblnr    LIKE   zeou_pcrdtl-mblnr,             "Number of Material Document
        whssn    LIKE   zeou_pcrdtl-whssn,             "Warehouse Records Entry Serial No.
        whsdt    LIKE   zeou_pcrdtl-whsdt,             "Warehouse Records Entry date
        END      OF     zeou_pcrdtl_itab.
DATA : BEGIN    OF     gr_wh_info OCCURS 0,          "INFO OF GR & WH BASED ON MVMT TYPE & PO
        mblnr    LIKE   mseg-mblnr,                    "Number of Material Document
        bldat    LIKE   mkpf-bldat,                    "Document Date in Document
        ebeln    LIKE   mseg-ebeln,                    "Purchasing Document Number
        ebelp    LIKE   ekpo-ebelp,                    "Item Number of Purchasing Document
        matnr    LIKE   mseg-matnr,                    "Material Number
        lifnr    LIKE   mseg-lifnr,                    "Account Number of the Vendor
        werks    LIKE   mseg-werks,                    "Plant
        menge    LIKE   mseg-menge,                    "Quantity
        dmbtr    LIKE   mseg-dmbtr,                    "Amount in local currency
        bwart    LIKE   mseg-bwart,                    "Movement Type (Inventory Management)
        whssn    LIKE   zeou_pcrdtl-whssn,             "Warehouse Records Entry Serial No.
        whsdt    LIKE   zeou_pcrdtl-whsdt,             "Warehouse Records Entry date
        END      OF     gr_wh_info.
DATA : BEGIN    OF     bseg_itab OCCURS 0,
        ebeln    LIKE   bseg-ebeln,                    "Purchasing Document Number
        ebelp    LIKE   bseg-ebelp,                    "Item Number of Purchasing Document
        matnr    LIKE   bseg-matnr,                    "Material Number
        lifnr    LIKE   bseg-lifnr,                    "Account Number of the Vendor
        werks    LIKE   bseg-werks,                    "Plant
        buzid    LIKE   bseg-buzid,                    "Identification of the Line Item
        bschl    LIKE   bseg-bschl,                    "Posting Key
        wrbtr    LIKE   bseg-wrbtr,                    "Amount in document currency
        bukrs    LIKE   bseg-bukrs,                    "Company Code
        belnr    LIKE   bseg-belnr,                    "Accounting Document Number
        gjahr    LIKE   bseg-gjahr,                    "Fiscal Year
        END      OF     bseg_itab.
DATA : BEGIN    OF     bkpf_itab OCCURS 0,
        bukrs    LIKE   bkpf-bukrs,                    "Company Code
        belnr    LIKE   bkpf-belnr,                    "Accounting Document Number
        gjahr    LIKE   bkpf-gjahr,                    "Fiscal Year
        xblnr    LIKE   bkpf-xblnr,                    "Reference Document Number
        bldat    LIKE   bkpf-bldat,                    "Document Date in Document
        END      OF     bkpf_itab.
DATA : BEGIN    OF     vend_inv OCCURS 0,            "VENDOR INVOICE DETAILS
        ebeln    LIKE   bseg-ebeln,                    "Purchasing Document Number
        ebelp    LIKE   bseg-ebelp,                    "Item Number of Purchasing Document
        matnr    LIKE   bseg-matnr,                    "Material Number
        lifnr    LIKE   bseg-lifnr,                    "Account Number of the Vendor
        werks    LIKE   bseg-werks,                    "Plant
        buzid    LIKE   bseg-buzid,                    "Identification of the Line Item
        bschl    LIKE   bseg-bschl,                    "Posting Key
        wrbtr    LIKE   bseg-wrbtr,                    "Amount in document currency
        bukrs    LIKE   bseg-bukrs,                    "Company Code
        belnr    LIKE   bseg-belnr,                    "Accounting Document Number
        gjahr    LIKE   bseg-gjahr,                    "Fiscal Year
        xblnr    LIKE   bkpf-xblnr,                    "Reference Document Number
        bldat    LIKE   bkpf-bldat,                    "Document Date in Document
        END      OF     vend_inv.
DATA : BEGIN    OF     chckinit OCCURS 0,            "CHEQUE INIT INFO
        ebeln    LIKE   bseg-ebeln,                    "Purchasing Document Number
        ebelp    LIKE   bseg-ebelp,                    "Item Number of Purchasing Document
        matnr    LIKE   bseg-matnr,                    "Material Number
        lifnr    LIKE   bseg-lifnr,                    "Account Number of the Vendor
        werks    LIKE   bseg-werks,                    "Plant
        buzid    LIKE   bseg-buzid,                    "Identification of the Line Item
        bschl    LIKE   bseg-bschl,                    "Posting Key
        bukrs    LIKE   bkpf-bukrs,                    "Company Code
        belnr    LIKE   bkpf-belnr,                    "Accounting Document Number
        gjahr    LIKE   bkpf-gjahr,                    "Fiscal Year
        koart    LIKE   bseg-koart,                    "Account type
        augbl    LIKE   bseg-augbl,                    "Document Number of the Clearing Document
        END      OF     chckinit.
DATA : BEGIN    OF     chckpayer OCCURS 0,           "CHEQUE BANK DETAILS
        vblnr    LIKE   payr-vblnr,                    "Document Number of the Payment Document
        zbukr    LIKE   payr-zbukr,                    "Paying company code
        gjahr    LIKE   payr-gjahr,                    "Fiscal Year
        chect    LIKE   payr-chect,                    "Check Number
        zaldt    LIKE   payr-zaldt,                    "Probable Payment Date (Cash Discount 1 Due)
        hbkid    LIKE   payr-hbkid,                    "Short key for a house bank
        END      OF     chckpayer.
DATA : chckpayer_u LIKE chckpayer OCCURS 0 WITH HEADER LINE.      "UNIQUE CHEQUE DETAILS
DATA : BEGIN    OF     chckfinal OCCURS 0,           "CHEQUE FINAL INFO
        ebeln    LIKE   bseg-ebeln,                    "Purchasing Document Number
        ebelp    LIKE   bseg-ebelp,                    "Item Number of Purchasing Document
        matnr    LIKE   bseg-matnr,                    "Material Number
        lifnr    LIKE   bseg-lifnr,                    "Account Number of the Vendor
        werks    LIKE   bseg-werks,                    "Plant
        buzid    LIKE   bseg-buzid,                    "Identification of the Line Item
        bschl    LIKE   bseg-bschl,                    "Posting Key
        bukrs    LIKE   bkpf-bukrs,                    "Company Code
        belnr    LIKE   bkpf-belnr,                    "Accounting Document Number
        gjahr    LIKE   bkpf-gjahr,                    "Fiscal Year
        koart    LIKE   bseg-koart,                    "Account type
        augbl    LIKE   bseg-augbl,                    "Document Number of the Clearing Document
        vblnr    LIKE   payr-vblnr,                    "Document Number of the Payment Document
        zbukr    LIKE   payr-zbukr,                    "Paying company code
        chect    LIKE   payr-chect,                    "Check Number
        zaldt    LIKE   payr-zaldt,                    "Probable Payment Date (Cash Discount 1 Due)
        hbkid    LIKE   payr-hbkid,                    "Short key for a house bank
        END      OF     chckfinal.
DATA : BEGIN    OF     mat_desc OCCURS 0,
        matnr    LIKE   mara-matnr,
        maktx    LIKE   makt-maktx,
        END      OF     mat_desc.
DATA : BEGIN      OF     vend_det OCCURS 0,
        lifnr      LIKE   lfa1-lifnr,
        name1      LIKE   lfa1-name1,
        j_1icstno LIKE   j_1imovend-j_1icstno,
        END        OF     vend_det.
DATA : BEGIN    OF     cst_rep OCCURS 0,             "FINAL CST REPORT
        lifnr    LIKE   a363-lifnr,                    "Account Number of the Vendor
        name1    LIKE   lfa1-name1,                    "Vendor Name
        j_1icstno LIKE   j_1imovend-j_1icstno,        " Vendor CST No.
        werks    LIKE   a363-werks,                    "Plant
       kschl    LIKE   a363-kschl,                    "Condition type
        ebeln    LIKE   ekko-ebeln,                    "Purchasing Document Number
        ebelp    LIKE   ekpo-ebelp,                    "Item Number of Purchasing Document
        bedat    LIKE   ekko-bedat,                    "Purchasing Document Date
        matnr    LIKE   ekpo-matnr,                    "Material Number
        maktx    LIKE   makt-maktx,                    "Material Description.
        kbetr    LIKE   konp-kbetr,                    "Rate (condition amount or percentage) where no scale exists
        mblnr    LIKE   mseg-mblnr,                    "Number of Material Document
        bldat    LIKE   mkpf-bldat,                    "Document Date in Document
        menge    LIKE   mseg-menge,                    "Quantity
        dmbtr    LIKE   mseg-dmbtr,                    "Amount in local currency
        cst_dmbtr LIKE mseg-dmbtr,                    "CST Amount in local currency
        bwart    LIKE   mseg-bwart,                    "Movement Type (Inventory Management)
        whssn    LIKE   zeou_pcrdtl-whssn,             "Warehouse Records Entry Serial No.
        whsdt    LIKE   zeou_pcrdtl-whsdt,             "Warehouse Records Entry date
        buzid    LIKE   bseg-buzid,                    "Identification of the Line Item
        bschl    LIKE   bseg-bschl,                    "Posting Key
        wrbtr    LIKE   bseg-wrbtr,                    "Amount in document currency
        cst_wrbtr LIKE bseg-wrbtr,                    "CST Amount in document currency
        belnr    LIKE   bseg-belnr,                    "Accounting Document Number
        gjahr    LIKE   bseg-gjahr,                    "Fiscal Year
        xblnr    LIKE   bkpf-xblnr,                    "Reference Document Number
        koart    LIKE   bseg-koart,                    "Account type
        augbl    LIKE   bseg-augbl,                    "Document Number of the Clearing Document
        vblnr    LIKE   payr-vblnr,                    "Document Number of the Payment Document
        zbukr    LIKE   payr-zbukr,                    "Paying company code
        chect    LIKE   payr-chect,                    "Check Number
        zaldt    LIKE   payr-zaldt,                    "Probable Payment Date (Cash Discount 1 Due)
        hbkid    LIKE   payr-hbkid,                    "Short key for a house bank
        END      OF     cst_rep.
DATA : BEGIN    OF     gt_output OCCURS 0,              "ALV OUTPUT
        slno     LIKE   sy-tabix,                      "Serial Number
        lifnr    LIKE   a363-lifnr,                    "Account Number of the Vendor
        name1    LIKE   lfa1-name1,                    "Vendor Name
        j_1icstno LIKE   j_1imovend-j_1icstno,        " Vendor CST No.
        werks    LIKE   a363-werks,                    "Plant
       kschl    LIKE   a363-kschl,                    "Condition type
        ebeln    LIKE   ekko-ebeln,                    "Purchasing Document Number
        ebelp    LIKE   ekpo-ebelp,                    "Item Number of Purchasing Document
        bedat    LIKE   ekko-bedat,                    "Purchasing Document Date
        matnr    LIKE   ekpo-matnr,                    "Material Number
        maktx    LIKE   makt-maktx,                    "Material Description
        mblnr    LIKE   mseg-mblnr,                    "Number of Material Document
        bldat    LIKE   mkpf-bldat,                    "Document Date in Document
        menge    LIKE   mseg-menge,                    "Quantity
        dmbtr    LIKE   mseg-dmbtr,                    "Amount in local currency
        cst_dmbtr LIKE mseg-dmbtr,                    "CST Amount in local currency
        bwart    LIKE   mseg-bwart,                    "Movement Type (Inventory Management)
        whssn    LIKE   zeou_pcrdtl-whssn,             "Warehouse Records Entry Serial No.
        whsdt    LIKE   zeou_pcrdtl-whsdt,             "Warehouse Records Entry date
        buzid    LIKE   bseg-buzid,                    "Identification of the Line Item
        bschl    LIKE   bseg-bschl,                    "Posting Key
        wrbtr    LIKE   bseg-wrbtr,                    "Amount in document currency
        cst_wrbtr LIKE bseg-wrbtr,                    "CST Amount in document currency
        belnr    LIKE   bseg-belnr,                    "Accounting Document Number
        gjahr    LIKE   bseg-gjahr,                    "Fiscal Year
        xblnr    LIKE   bkpf-xblnr,                    "Reference Document Number
        koart    LIKE   bseg-koart,                    "Account type
        augbl    LIKE   bseg-augbl,                    "Document Number of the Clearing Document
        vblnr    LIKE   payr-vblnr,                    "Document Number of the Payment Document
        zbukr    LIKE   payr-zbukr,                    "Paying company code
        chect    LIKE   payr-chect,                    "Check Number
        zaldt    LIKE   payr-zaldt,                    "Probable Payment Date (Cash Discount 1 Due)
        hbkid    LIKE   payr-hbkid,                    "Short key for a house bank
        usr_txt1(20) TYPE c,
        usr_txt2(20) TYPE c,
        END      OF     gt_output.
*Working Variables
DATA : cst_gr LIKE mseg-dmbtr,
       cst_inv LIKE bseg-wrbtr,
       usr_txt1(20) TYPE c,
       usr_txt2(20) TYPE c.
START-OF-SELECTION.
*Retreiving Data from a363 table for the given input
SELECT matnr
          lifnr
          werks
          kschl
          knumh
          FROM a363
          INTO TABLE a363_itab
          WHERE matnr IN s_matnr AND lifnr IN s_lifnr AND werks EQ p_werks AND kschl IN s_kschl.
SELECT *
          FROM konp
          INTO CORRESPONDING FIELDS OF TABLE konp_itab
          FOR ALL ENTRIES IN a363_itab
          WHERE knumh EQ a363_itab-knumh.
LOOP AT a363_itab.
    READ TABLE konp_itab WITH KEY knumh = a363_itab-knumh.
    IF sy-subrc EQ 0.
      MOVE : konp_itab-kbetr TO a363_itab-kbetr.
      MODIFY a363_itab.
    ENDIF.
    CLEAR : a363_itab, konp_itab.
ENDLOOP.
SELECT *
         FROM makt
         INTO CORRESPONDING FIELDS OF TABLE mat_desc
         FOR ALL ENTRIES IN a363_itab
         WHERE matnr EQ a363_itab-matnr.
SELECT a~lifnr
         a~name1
         b~j_1icstno
         INTO TABLE vend_det
         FROM lfa1 AS a JOIN j_1imovend AS b
         ON alifnr EQ blifnr
         FOR ALL ENTRIES IN a363_itab
         WHERE a~lifnr EQ a363_itab-lifnr.
Retreiving Data from EKKO & EKPO table for the given input
And Populating the V_PO_DETAILS itab
SELECT *
          FROM ekko
          INTO CORRESPONDING FIELDS OF TABLE ekko_itab
          FOR ALL ENTRIES IN a363_itab
          WHERE lifnr EQ a363_itab-lifnr AND bedat IN s_bedat.
SELECT *
          FROM ekpo
          INTO CORRESPONDING FIELDS OF TABLE ekpo_itab
          FOR ALL ENTRIES IN a363_itab
          WHERE matnr EQ a363_itab-matnr AND werks EQ a363_itab-werks AND mwskz NE 'V0'.
LOOP AT ekpo_itab.
    MOVE :   ekpo_itab-ebelp TO v_po_det-ebelp,
             ekpo_itab-matnr TO v_po_det-matnr,
             ekpo_itab-werks TO v_po_det-werks,
             ekpo_itab-menge TO v_po_det-menge.
    READ TABLE ekko_itab WITH KEY ebeln = ekpo_itab-ebeln.
    IF sy-subrc EQ 0.
      MOVE : ekko_itab-lifnr TO v_po_det-lifnr,
               ekko_itab-ebeln TO v_po_det-ebeln,
               ekko_itab-bedat TO v_po_det-bedat.
      APPEND : v_po_det.
    ENDIF.
    CLEAR : ekko_itab, ekpo_itab, v_po_det.
ENDLOOP.
LOOP AT v_po_det.
    READ TABLE a363_itab WITH KEY matnr = v_po_det-matnr lifnr = v_po_det-lifnr werks = v_po_det-werks.
    IF sy-subrc EQ 0.
      MOVE : a363_itab-kbetr TO v_po_det-kbetr.
      MODIFY v_po_det.
    ENDIF.
    CLEAR : a363_itab, v_po_det.
ENDLOOP.
Retreiving Data from MKPF & MSEG & ZEOU_PCRDTL table for the given input
And Populating the GR_WH_info itab
SELECT *
          FROM mseg
          INTO CORRESPONDING FIELDS OF TABLE mseg_itab
          FOR ALL ENTRIES IN v_po_det
          WHERE ebeln EQ v_po_det-ebeln AND matnr EQ v_po_det-matnr AND bwart IN s_bwart.
SELECT *
          FROM mkpf
          INTO CORRESPONDING FIELDS OF TABLE mkpf_itab
          FOR ALL ENTRIES IN mseg_itab
          WHERE mblnr EQ mseg_itab-mblnr.
SELECT *
          FROM zeou_pcrdtl
          INTO CORRESPONDING FIELDS OF TABLE zeou_pcrdtl_itab
          FOR ALL ENTRIES IN mseg_itab
          WHERE mblnr EQ mseg_itab-mblnr AND matnr EQ mseg_itab-matnr.
LOOP AT mseg_itab.
    MOVE : mseg_itab-mblnr TO gr_wh_info-mblnr,
             mseg_itab-ebeln TO gr_wh_info-ebeln,
             mseg_itab-ebelp TO gr_wh_info-ebelp,
             mseg_itab-matnr TO gr_wh_info-matnr,
             mseg_itab-lifnr TO gr_wh_info-lifnr,
             mseg_itab-werks TO gr_wh_info-werks,
             mseg_itab-menge TO gr_wh_info-menge,
             mseg_itab-dmbtr TO gr_wh_info-dmbtr,
             mseg_itab-bwart TO gr_wh_info-bwart.
    READ TABLE mkpf_itab WITH KEY mblnr = mseg_itab-mblnr.
    IF sy-subrc EQ 0.
      MOVE : mkpf_itab-bldat TO gr_wh_info-bldat.
    ENDIF.
    READ TABLE zeou_pcrdtl_itab WITH KEY mblnr = mseg_itab-mblnr.
    IF sy-subrc EQ 0.
      MOVE : zeou_pcrdtl_itab-whssn TO gr_wh_info-whssn,
               zeou_pcrdtl_itab-whsdt TO gr_wh_info-whsdt.
    ENDIF.
    APPEND : gr_wh_info.
    CLEAR : mseg_itab, mkpf_itab, gr_wh_info.
ENDLOOP.
Retreiving Data from BSEG & BKPF table
And Populating the Vendor Invoice Details
SELECT *
          FROM bseg
          INTO CORRESPONDING FIELDS OF TABLE bseg_itab
          FOR ALL ENTRIES IN v_po_det
          WHERE ebeln EQ v_po_det-ebeln AND matnr EQ v_po_det-matnr AND buzid EQ 'W' AND bschl EQ '96'.
SELECT *
          FROM bkpf
          INTO CORRESPONDING FIELDS OF TABLE bkpf_itab
          FOR ALL ENTRIES IN bseg_itab
          WHERE bukrs EQ bseg_itab-bukrs AND belnr EQ bseg_itab-belnr AND gjahr EQ bseg_itab-gjahr.
LOOP AT bseg_itab.
    MOVE : bseg_itab-ebeln TO vend_inv-ebeln,
             bseg_itab-ebelp TO vend_inv-ebelp,
             bseg_itab-matnr TO vend_inv-matnr,
             bseg_itab-lifnr TO vend_inv-lifnr,
             bseg_itab-werks TO vend_inv-werks,
             bseg_itab-buzid TO vend_inv-buzid,
             bseg_itab-bschl TO vend_inv-bschl,
             bseg_itab-wrbtr TO vend_inv-wrbtr,
             bseg_itab-bukrs TO vend_inv-bukrs,
             bseg_itab-belnr TO vend_inv-belnr,
             bseg_itab-gjahr TO vend_inv-gjahr.
    READ TABLE bkpf_itab WITH KEY bukrs = bseg_itab-bukrs belnr = bseg_itab-belnr gjahr = bseg_itab-gjahr.
    IF sy-subrc EQ 0.
      MOVE : bkpf_itab-xblnr TO vend_inv-xblnr,
               bkpf_itab-bldat TO vend_inv-bldat.
      APPEND : vend_inv.
    ENDIF.
    CLEAR : vend_inv, bseg_itab, bkpf_itab.
ENDLOOP.
Retreiving Data from BSEG & BKPF table
And Populating the Cheque Info Details
SELECT *
          FROM bseg
          INTO CORRESPONDING FIELDS OF TABLE chckinit
          FOR ALL ENTRIES IN v_po_det
          WHERE ebeln EQ v_po_det-ebeln AND matnr EQ v_po_det-matnr AND buzid EQ 'W' AND bschl EQ '86' AND koart EQ 'K'.
SELECT *
          FROM payr
          INTO CORRESPONDING FIELDS OF TABLE chckpayer
          FOR ALL ENTRIES IN chckinit
          WHERE vblnr EQ chckinit-augbl.
SORT chckpayer BY vblnr DESCENDING.
LOOP AT chckpayer.
    ON CHANGE OF chckpayer-vblnr.
      MOVE   : chckpayer TO chckpayer_u.
      APPEND : chckpayer_u.
      CLEAR : chckpayer_u, chckpayer.
    ENDON.
ENDLOOP.
LOOP AT chckinit.
    MOVE : chckinit-ebeln TO chckfinal-ebeln,
             chckinit-ebelp TO chckfinal-ebelp,
             chckinit-matnr TO chckfinal-matnr,
             chckinit-lifnr TO chckfinal-lifnr,
             chckinit-werks TO chckfinal-werks,
             chckinit-buzid TO chckfinal-buzid,
             chckinit-bschl TO chckfinal-bschl,
             chckinit-bukrs TO chckfinal-bukrs,
             chckinit-gjahr TO chckfinal-gjahr,
             chckinit-koart TO chckfinal-koart,
             chckinit-augbl TO chckfinal-augbl.
    READ TABLE chckpayer_u WITH KEY vblnr = chckinit-augbl gjahr = chckinit-gjahr.
    IF sy-subrc EQ 0.
      MOVE : chckpayer_u-vblnr TO chckfinal-vblnr,
               chckpayer_u-zbukr TO chckfinal-zbukr,
               chckpayer_u-chect TO chckfinal-chect,
               chckpayer_u-zaldt TO chckfinal-zaldt,
               chckpayer_u-hbkid TO chckfinal-hbkid.
      APPEND : chckfinal.
    ENDIF.
    CLEAR : chckfinal, chckpayer_u, chckinit.
ENDLOOP.
Populating the final CST TABLE
LOOP AT v_po_det.
    MOVE :   v_po_det-lifnr TO cst_rep-lifnr,
              v_po_det-werks TO cst_rep-werks,
              v_po_det-ebeln TO cst_rep-ebeln,
              v_po_det-ebelp TO cst_rep-ebelp,
              v_po_det-bedat TO cst_rep-bedat,
              v_po_det-matnr TO cst_rep-matnr,
              v_po_det-kbetr TO cst_rep-kbetr.
    READ TABLE gr_wh_info WITH KEY ebeln = v_po_det-ebeln ebelp = v_po_det-ebelp."matnr = v_po_det-matnr.
    IF sy-subrc EQ 0.
      MOVE : gr_wh_info-mblnr TO cst_rep-mblnr,
              gr_wh_info-bldat TO cst_rep-bldat,
              gr_wh_info-menge TO cst_rep-menge,
              gr_wh_info-dmbtr TO cst_rep-dmbtr,
              gr_wh_info-bwart TO cst_rep-bwart,
              gr_wh_info-whssn TO cst_rep-whssn,
              gr_wh_info-whsdt TO cst_rep-whsdt.
    ENDIF.
    READ TABLE vend_inv WITH KEY ebeln = v_po_det-ebeln ebelp = v_po_det-ebelp."matnr = v_po_det-matnr.
    IF sy-subrc EQ 0.
      MOVE : vend_inv-buzid TO cst_rep-buzid,
             vend_inv-bschl TO cst_rep-bschl,
             vend_inv-wrbtr TO cst_rep-wrbtr,
             vend_inv-belnr TO cst_rep-belnr,
             vend_inv-gjahr TO cst_rep-gjahr,
             vend_inv-xblnr TO cst_rep-xblnr.
    ENDIF.
    READ TABLE chckfinal WITH KEY ebeln = v_po_det-ebeln ebelp = v_po_det-ebelp."matnr = v_po_det-matnr.
    IF sy-subrc EQ 0.
      MOVE : chckfinal-augbl TO cst_rep-augbl,
             chckfinal-vblnr TO cst_rep-vblnr,
             chckfinal-zbukr TO cst_rep-zbukr,
             chckfinal-chect TO cst_rep-chect,
             chckfinal-zaldt TO cst_rep-zaldt,
             chckfinal-hbkid TO cst_rep-hbkid.
    ENDIF.
    READ TABLE mat_desc WITH KEY matnr = v_po_det-matnr.
    IF sy-subrc EQ 0.
      MOVE : mat_desc-maktx TO cst_rep-maktx.
    ENDIF.
    READ TABLE vend_det WITH KEY lifnr = v_po_det-lifnr.
    IF sy-subrc EQ 0.
      MOVE : vend_det-name1 TO cst_rep-name1,
             vend_det-j_1icstno TO cst_rep-j_1icstno.
    ENDIF.
    APPEND : cst_rep.
    CLEAR : cst_rep, v_po_det, gr_wh_info, vend_inv, chckfinal.
ENDLOOP.
Populating GT_output
LOOP AT cst_rep.
    cst_gr = cst_rep-dmbtr * ( cst_rep-kbetr / 1000 ).
    cst_inv = cst_rep-wrbtr * ( cst_rep-kbetr / 1000 ).
    MOVE : cst_gr TO cst_rep-cst_dmbtr,
           cst_inv TO cst_rep-cst_wrbtr.
    MODIFY : cst_rep.
    CLEAR : cst_rep, cst_gr, cst_inv.
ENDLOOP.
LOOP AT cst_rep.
    MOVE : sy-tabix TO gt_output-slno,
            cst_rep-lifnr TO gt_output-lifnr,
            cst_rep-name1 TO gt_output-name1,
            cst_rep-j_1icstno TO gt_output-j_1icstno,
            cst_rep-werks TO gt_output-werks,
            cst_rep-matnr TO gt_output-matnr,
            cst_rep-maktx TO gt_output-maktx,
            cst_rep-ebeln TO gt_output-ebeln,
            cst_rep-ebelp TO gt_output-ebelp,
            cst_rep-bedat TO gt_output-bedat,
            cst_rep-mblnr TO gt_output-mblnr,
            cst_rep-bldat TO gt_output-bldat,
            cst_rep-menge TO gt_output-menge,
            cst_rep-dmbtr TO gt_output-dmbtr,
            cst_rep-cst_dmbtr TO gt_output-cst_dmbtr,
            cst_rep-bwart TO gt_output-bwart,
            cst_rep-whssn TO gt_output-whssn,
            cst_rep-whsdt TO gt_output-whsdt,
            cst_rep-buzid TO gt_output-buzid,
            cst_rep-bschl TO gt_output-bschl,
            cst_rep-wrbtr TO gt_output-wrbtr,
            cst_rep-cst_wrbtr TO gt_output-cst_wrbtr,
            cst_rep-belnr TO gt_output-belnr,
            cst_rep-gjahr TO gt_output-gjahr,
            cst_rep-xblnr TO gt_output-xblnr,
            cst_rep-augbl TO gt_output-augbl,
            cst_rep-vblnr TO gt_output-vblnr,
            cst_rep-zbukr TO gt_output-zbukr,
            cst_rep-chect TO gt_output-chect,
            cst_rep-zaldt TO gt_output-zaldt,
            cst_rep-hbkid TO gt_output-hbkid.
    APPEND gt_output.
    CLEAR : cst_rep, gt_output, sy-tabix.
ENDLOOP.
END-OF-SELECTION.
*-ALV Routine
PERFORM alv_forms.
*&      Form alv_forms
FORM alv_forms.
PERFORM alv_routines.
gx_variant = sy-repid.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
    EXPORTING
      i_save     = g_save
    CHANGING
      cs_variant = gx_variant
    EXCEPTIONS
      not_found = 2.
IF sy-subrc = 0.
    vari = gx_variant-variant.
ENDIF.
PERFORM comment_build USING gt_list_top_of_page[].
PERFORM fieldcat_init USING gt_fieldcat[].
PERFORM layout_build USING gs_layout.
PERFORM print_build USING gs_print.
PERFORM alv_output.
ENDFORM.                    " alv_forms
*&      Form alv_routines
FORM alv_routines.
PERFORM eventtab_build USING gt_events[].
PERFORM e06_t_sort_build USING gt_sort[].
PERFORM sp_group_build USING gt_sp_group[].
g_save = 'A'.
PERFORM variant_init.
ENDFORM.                    " alv_routines
*&      Form eventtab_build
FORM eventtab_build USING p_gt_events TYPE slis_t_event.
DATA: ls_event TYPE slis_alv_event.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
    EXPORTING
      i_list_type = 0
    IMPORTING
      et_events   = p_gt_events.
READ TABLE p_gt_events WITH KEY name = slis_ev_top_of_page
                         INTO ls_event.
IF sy-subrc = 0.
    MOVE slis_ev_top_of_page TO ls_event-form.
    APPEND ls_event TO p_gt_events.
ENDIF.
READ TABLE p_gt_events WITH KEY name = slis_ev_user_command
                         INTO ls_event.
IF sy-subrc = 0.
    MOVE slis_ev_user_command TO ls_event-form.
    APPEND ls_event TO p_gt_events.
ENDIF.
READ TABLE p_gt_events WITH KEY name = slis_ev_pf_status_set
                         INTO ls_event.
IF sy-subrc = 0.
    MOVE slis_ev_pf_status_set TO ls_event-form.
    APPEND ls_event TO p_gt_events.
ENDIF.
SORT p_gt_events BY name.
DELETE ADJACENT DUPLICATES FROM p_gt_events.
DELETE p_gt_events WHERE form IS INITIAL.
ENDFORM.                    " eventtab_build
*&      Form sort_build
FORM e06_t_sort_build USING e06_lt_sort TYPE slis_t_sortinfo_alv.
DATA: ls_sort TYPE slis_sortinfo_alv.
CLEAR ls_sort.
ls_sort-fieldname = 'SLNO'.
ls_sort-spos      = 1.
ls_sort-up        = 'X'.
APPEND ls_sort TO e06_lt_sort.
CLEAR ls_sort.
ls_sort-fieldname = 'CNCNR'.
ls_sort-spos      = 1.
ls_sort-up        = 'X'.
APPEND ls_sort TO e06_lt_sort.
CLEAR ls_sort.
ls_sort-fieldname = 'MATNR'.
ls_sort-spos      = 1.
ls_sort-up        = 'X'.
APPEND ls_sort TO e06_lt_sort.
ENDFORM.                    " sort_build
*&      Form sp_group_build
FORM sp_group_build USING    p_gt_sp_group TYPE slis_t_sp_group_alv.
DATA: ls_sp_group TYPE slis_sp_group_alv.
CLEAR ls_sp_group.
ls_sp_group-sp_group = 'A'.
ls_sp_group-text     = 'PRODUCT'.
APPEND ls_sp_group TO p_gt_sp_group.
ENDFORM.                    " sp_group_build
*&      Form variant_init
FORM variant_init.
CLEAR g_variant.
g_repid = sy-repid.
g_variant-report = g_repid.
ENDFORM.                    " variant_init
*&      Form comment_build
FORM comment_build USING   e04_lt_top_of_page TYPE slis_t_listheader.
DATA: ls_line     TYPE slis_listheader.
DATA: l_date(10) TYPE c,
        l_time(8)   TYPE c,
        l_out(255) TYPE c.
WRITE sy-datum TO l_date.
WRITE sy-uzeit TO l_time.
CONCATENATE l_date '/' l_time INTO l_out.
CLEAR ls_line.
ls_line-typ = 'H'.
CLEAR ls_line.
ls_line-typ = 'S'.
ls_line-key = 'RUN BY :'.
ls_line-info = sy-uname.
APPEND ls_line TO e04_lt_top_of_page.
CLEAR ls_line.
ls_line-typ = 'S'.
ls_line-key = 'RUN ON :'.
ls_line-info = l_out.
APPEND ls_line TO e04_lt_top_of_page.
ENDFORM.                    " comment_build
*&      Form fieldcat_init
FORM fieldcat_init    USING e01_lt_fieldcat TYPE slis_t_fieldcat_alv.
DATA: ls_fieldcat TYPE slis_fieldcat_alv.
DATA n1(3).
DATA count(2)    TYPE c.
DATA h1(10).
DATA: l_week     LIKE scal-week,
        l_text(17) TYPE c.
DATA cnt TYPE i.
cnt = cnt + 1.
CLEAR ls_fieldcat.
ls_fieldcat-row_pos      = 1.
ls_fieldcat-col_pos      = 1.
ls_fieldcat-fieldname    = 'SLNO'.
ls_fieldcat-seltext_m    = 'SL.NO'.
ls_fieldcat-hotspot      = 'X'.
ls_fieldcat-key          = 'X'.
ls_fieldcat-key_sel      = 'X'.
ls_fieldcat-just         = 'R'.
ls_fieldcat-sp_group = 'A'.
APPEND ls_fieldcat TO e01_lt_fieldcat.
cnt = cnt + 1.
CLEAR ls_fieldcat.
ls_fieldcat-row_pos      = 1.
ls_fieldcat-col_pos      = cnt.
ls_fieldcat-fieldname    = 'LIFNR'.
ls_fieldcat-seltext_m    = 'VENDOR NO.'.
ls_fieldcat-hotspot      = 'X'.
ls_fieldcat-key          = 'X'.
ls_fieldcat-key_sel      = 'X'.
ls_fieldcat-just         = 'R'.
ls_fieldcat-sp_group = 'A'.
APPEND ls_fieldcat TO e01_lt_fieldcat.
cnt = cnt + 1.
CLEAR ls_fieldcat.
ls_fieldcat-row_pos      = 1.
ls_fieldcat-col_pos      = cnt.
ls_fieldcat-fieldname    = 'NAME1'.
ls_fieldcat-seltext_m    = 'VENDOR NAME'.
ls_fieldcat-hotspot      = 'X'.
ls_fieldcat-key          = 'X'.
ls_fieldcat-key_sel      = 'X'.
ls_fieldcat-just         = 'L'.
ls_fieldcat-sp_group = 'A'.
APPEND ls_fieldcat TO e01_lt_fieldcat.
cnt = cnt + 1.
CLEAR ls_fieldcat.
ls_fieldcat-row_pos      = 1.
ls_fieldcat-col_pos      = cnt.
ls_fieldcat-fieldname    = 'J_1ICSTNO'.
ls_fieldcat-seltext_m    = 'VENDOR CST NO.'.
ls_fieldcat-hotspot      = 'X'.
ls_fieldcat-key          = 'X'.
ls_fieldcat-key_sel      = 'X'.
ls_fieldcat-just         = 'R'.
ls_fieldcat-sp_group = 'A'.
APPEND ls_fieldcat TO e01_lt_fieldcat.
cnt = cnt + 1.
CLEAR ls_fieldcat.
ls_fieldcat-row_pos      = 1.
ls_fieldcat-col_pos      = cnt.
ls_fieldcat-fieldname    = 'WERKS'.
ls_fieldcat-seltext_m    = 'PLANT'.
ls_fieldcat-key          = 'X'.
ls_fieldcat-key_sel      = 'X'.
ls_fieldcat-just         = 'R'.
ls_fieldcat-sp_group = 'A'.
APPEND ls_fieldcat TO e01_lt_fieldcat.
cnt = cnt + 1.
CLEAR ls_fieldcat.
ls_fieldcat-row_pos      = 1.
ls_fieldcat-col_pos      = cnt.
ls_fieldcat-fieldname    = 'EBELN'.
ls_fieldcat-seltext_m    = 'PO NO.'.
ls_fieldcat-key          = 'X'.
ls_fieldcat-key_sel      = 'X'.
ls_fieldcat-just         = 'R'.
ls_fieldcat-sp_group = 'A'.
APPEND ls_fieldcat TO e01_lt_fieldcat.
cnt = cnt + 1.
CLEAR ls_fieldcat.
ls_fieldcat-row_pos      = 1.
ls_fieldcat-col_pos      = cnt.
ls_fieldcat-fieldname    = 'EBELP'.
ls_fieldcat-seltext_m    = 'PO ITEM'.
ls_fieldcat-key          = 'X'.
ls_fieldcat-key_sel      = 'X'.
ls_fieldcat-just         = 'R'.
ls_fieldcat-sp_group = 'A'.
APPEND ls_fieldcat TO e01_lt_fieldcat.
cnt = cnt + 1.
CLEAR ls_fieldcat.
ls_fieldcat-row_pos      = 1.
ls_fieldcat-col_pos      = cnt

Hi ,
This is a sort of performance issue , because your program takes more than the max time set for the program to execute in foreground.
There are many stuff in program which will hamper your performance.
I will list down a few
1. SELECT *
FROM konp
INTO CORRESPONDING FIELDS OF TABLE konp_itab
FOR ALL ENTRIES IN a363_itab
WHERE knumh EQ a363_itab-knumh
in this statement you are using for all entries a363_itab , but before this statement you are not checking if the table has any entry or not , please do remember that for all entries has this characterstic , that if you internal table does not contain any record , then all the records are selected from the database table. So in this case if you table a363_itab is empty , so what you want is no data must be seelcted from table konp , but what will happen is all the records in KONP will be seelcted.
2. While retreiving data you are using seelct * even though you do not require all the fields , an example is
<b>SELECT *
FROM mkpf
INTO CORRESPONDING FIELDS OF TABLE mkpf_itab
FOR ALL ENTRIES IN mseg_itab
WHERE mblnr EQ mseg_itab-mblnr.</b>
in this your internal table contains only 2 fields
<b>mblnr LIKE mkpf-mblnr, "Number of Material Document
bldat LIKE mkpf-bldat, "Document Date in Document</b> , but to get these 2 fields you are selecting all the fields of the table.
3. In select you are using into corresponding fields of table , it is not a good practice., so please avoidd it.
Please understand that you must try to reduce the access to your database tables and try to keep it minimal , because this same thing may happen becasue data in DEV is very less compared to the volume of data in production , so a program working in DEV will take much more time in PRD if not written properly and may result in timeouts , as in your case.
Please try to make chanegs to the prorgam and see if it works.
In case you have more queries , please do revert back.
Regards
Arun
*Reward points if replay is helpful

11.5.10.2 to R12.1.1 upgrade : AutoPatch warning : Product Data File $APPL_TOP/admin/*prod.txt does not exist for product

Hello Sir,
OS version : AIX 6.1
DB version : 11.2.0.3
EBS version : 11.5.10.2
As a part of 11.5.10.2 to R12.1.1 upgrade, I am applying merged patch (9179588:R12.AD.B) with 9477107:R12.AD.B and patch 7461070(R12.AD.B.1 upgrade driver).
I can see AutoPatch warning messages during adpatch session as below so I have not yet started this merged patch. Please suggest.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
drix10:/fmstop/patches/R1211AD/merge>adpatch
                     Copyright (c) 2002 Oracle Corporation
                        Redwood Shores, California, USA
                         Oracle Applications AutoPatch
                                 Version 12.0.0
NOTE: You may not use this utility for custom development
      unless you have written permission from Oracle Corporation.
Attention: AutoPatch no longer checks for unapplied pre-requisite patches.
You must use OAM Patch Wizard for this feature. Alternatively, you can
review the README for pre-requisite information.
Your default directory is '/fmstop/r12apps/apps/apps_st/appl'.
Is this the correct APPL_TOP [Yes] ?
AutoPatch records your AutoPatch session in a text file
you specify. Enter your AutoPatch log file name or press [Return]
to accept the default file name shown in brackets.
Filename [adpatch.log] : adpatch_u_merged_R12AD11.log
You can be notified by email if a failure occurs.
Do you wish to activate this feature [No] ?
Please enter the batchsize [1000] : 2000
Please enter the name of the Oracle Applications System that this
APPL_TOP belongs to.
The Applications System name must be unique across all Oracle
Applications Systems at your site, must be from 1 to 30 characters
long, may only contain alphanumeric and underscore characters,
and must start with a letter.
Sample Applications System names are: "prod", "test", "demo" and
"Development_2".
Applications System Name [FMSTEST] : FMSTEST *
NOTE: If you do not currently have certain types of files installed
in this APPL_TOP, you may not be able to perform certain tasks.
Example 1: If you don't have files used for installing or upgrading
the database installed in this area, you cannot install or upgrade
the database from this APPL_TOP.
Example 2: If you don't have forms files installed in this area, you cannot
generate them or run them from this APPL_TOP.
Example 3: If you don't have concurrent program files installed in this area,
you cannot relink concurrent programs or generate reports from this APPL_TOP.
Do you currently have files used for installing or upgrading the database
installed in this APPL_TOP [YES] ? YES *
Do you currently have Java and HTML files for HTML-based functionality
installed in this APPL_TOP [YES] ? YES *
Do you currently have Oracle Applications forms files installed
in this APPL_TOP [YES] ? YES *
Do you currently have concurrent program files installed
in this APPL_TOP [YES] ? YES *
Please enter the name Oracle Applications will use to identify this APPL_TOP.
The APPL_TOP name you select must be unique within an Oracle Applications
System, must be from 1 to 30 characters long, may only contain
alphanumeric and underscore characters, and must start with a letter.
Sample APPL_TOP Names are: "prod_all", "demo3_forms2", and "forms1".
APPL_TOP Name [drix10] : drix10 *
You are about to apply a patch to the installation of Oracle Applications
in your ORACLE database 'FMSTEST'
using ORACLE executables in '/fmstop/r12apps/apps/tech_st/10.1.2'.
Is this the correct database [Yes] ?
AutoPatch needs the password for your 'SYSTEM' ORACLE schema
in order to determine your installation configuration.
Enter the password for your 'SYSTEM' ORACLE schema:
The ORACLE username specified below for Application Object Library
uniquely identifies your existing product group: APPLSYS
Enter the ORACLE password of Application Object Library [APPS] :
AutoPatch is verifying your username/password.
The status of various features in this run of AutoPatch is:
                                           <-Feature version in->
Feature                          Active?   APPLTOP    Data model    Flags
CHECKFILE                        Yes       1          1             Y N N Y N Y
PREREQ                           Yes       6          6             Y N N Y N Y
CONCURRENT_SESSIONS              No        2          2             Y Y N Y Y N
PATCH_TIMING                     Yes       2          2             Y N N Y N Y
PATCH_HIST_IN_DB                 Yes       6          6             Y N N Y N Y
SCHEMA_SWAP                      Yes       1          1             Y N N Y Y Y
JAVA_WORKER                      No        1          -1            Y N N Y N N
CODELEVEL                        No        1          -1            Y N N Y N N
Identifier for the current session is 2987
Reading product information from file...
Reading language and territory information from file...
Reading language information from applUS.txt ...
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/eaaprod.txt
does not exist for product "eaa".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/abmprod.txt
does not exist for product "abm".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/evmprod.txt
does not exist for product "evm".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/ipdprod.txt
does not exist for product "ipd".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/zfaprod.txt
does not exist for product "zfa".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/zsaprod.txt
does not exist for product "zsa".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/cssprod.txt
does not exist for product "css".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/meprod.txt
does not exist for product "me".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/xnmprod.txt
does not exist for product "xnm".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/xncprod.txt
does not exist for product "xnc".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/xnsprod.txt
does not exist for product "xns".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/fptprod.txt
does not exist for product "fpt".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/okrprod.txt
does not exist for product "okr".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/cueprod.txt
does not exist for product "cue".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/ibaprod.txt
does not exist for product "iba".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/ozpprod.txt
does not exist for product "ozp".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/ozsprod.txt
does not exist for product "ozs".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/rlaprod.txt
does not exist for product "rla".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/vehprod.txt
does not exist for product "veh".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/rhxprod.txt
does not exist for product "rhx".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/imtprod.txt
does not exist for product "imt".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/ahmprod.txt
does not exist for product "ahm".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/okbprod.txt
does not exist for product "okb".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/okoprod.txt
does not exist for product "oko".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/xniprod.txt
does not exist for product "xni".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/jtsprod.txt
does not exist for product "jts".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/amfprod.txt
does not exist for product "amf".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Product Data File
/fmstop/r12apps/apps/apps_st/appl/admin/cunprod.txt
does not exist for product "cun".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
Reading database to see what industry is currently installed.
Reading FND_LANGUAGES to see what is currently installed.
Currently, the following language is installed:
Code   Language                                Status
US     American English                        Base
Your base language will be AMERICAN.
Setting up module information.
Reading database for information about the modules.
Saving module information.
Reading database for information about the products.
Reading database for information about how products depend on each other.
Reading topfile.txt ...
Saving product information.
Trying to obtain a lock...
Attempting to instantiate the current-view snapshot...
No baseline bug-fixes info available. Will attempt next time.
     **************** S T A R T   O F   U P L O A D ****************
Start date: Sun Aug 04 2013 18:45:12
0 "left over" javaupdates.txt files uploaded to DB: Sun Aug 04 2013 18:45:12
0 patches uploaded from the ADPSV format patch history files: Sun Aug 04 2013 18:45:12
Uploading information about files copied during the previous runs ...
0 "left over" filescopied_<session_id>.txt files uploaded to DB: Sun Aug 04 2013 18:45:12
     ****************** E N D   O F   U P L O A D ******************
End date: Sun Aug 04 2013 18:45:12
Enter the directory where your Oracle Applications patch has been unloaded
The default directory is [/fmstop/patches/R1211AD/merge] :
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

I checked under 11i $APPL_TOP/admin directory, I can see only one izuprod.txt file apart from applprod.txt.
drix10:/fmstop/fmstest/fmstestappl/admin>ls -lrt *prod.txt
-rwxr-xr-x    1 appltest dba          231650 Oct 30 2004 applprod.txt
-rwxr-xr-x    1 appltest dba            4966 Sep 21 2007 izuprod.txt
R12 code tree is newly installed so there is only applprod.txt
drix10:/fmstop/r12apps/apps/apps_st/appl/admin>ls -lrt *prod.txt
-rwxr-xr-x    1 appltest dba          226340 Jul 29 15:19 applprod.txt
Please suggest if I can ignore these warning to proceed with applying merged patch.

FAGLL03 Special Field Values Do Not Display in Production

We are using the new GL in ECC 6. I have a strange problem where special fields that were added to the line item transactions display in dev and quality but not in production. Please read the steps that I have taken.
1. Using note 984305 we defined special field BSEG-MATNR using this path:
Financial Accounting (New)
General Ledger Accounting (New)
    Master Data
      G/L Accounts
        Line Items
          Define Special Fields for Line Item Display
This field (U_MATNR) displays correctly in FAGLL03.
2. I used note 1034354 to create an implementation of BAdI 'FAGL_ITEMS_CH_DATA. Then I
followed the documentation of the BAdI to create structure CI_FAGLPOSX within FAGLPOSX and added these fields:
Material Type: field MARA-MTART
Material Group: MARA-MATKL
I added code to method CHANGE_ITEMS to read for those fields. Here's part of the code:
* MARA - Get Material Type and Material Group
    SELECT SINGLE mtart matkl
      FROM mara
      INTO (wa_items-zzmtart, wa_items-zzmatkl)
      WHERE matnr = wa_items-u_matnr.
The values of these fields display correctly in development and quality, but they do not display in production.
3. When I debugged FAGLL03 in development I found that the value of U_MATNR was filled when I stopped at method CHANGE_ITEMS. However, when I debugged in production, U_MATNR was not filled. It had to be filled at a later time because the value appears on the report. In my code, I am using U_MATNR to find the values of material type and material group. Because U_MATNR doesn't have a value at that point in time in production, my code doesn't find material type or material group.
4. I contacted SAP and was instructed to use note 984305. I executed the function module
ITEM_STRUC_EXTENSION which did not help.
5 I also used note 205096 to execute report BALVBUFDEL, but this did not help either.
6. At this point, SAP told me that it is a consulting issue. I'm not sure that it is because I'm using SAP solutions without modifying anything.
7. I tried to compare configuration between development and production, but everything looked OK to me.
Has anyone had this problem? Any tips?
Brenda

Hi Brenda,
>
Brenda Bankert wrote:
> 6. At this point, SAP told me that it is a consulting issue. I'm not sure that it is because I'm using SAP solutions without modifying anything.
I have no idea except that you can make sure Include CI_FAGLPOSX is active as well as the including FAGLPOSX. And please check the transport protocol(s) if CI_FAGLPOSX is included. If you have any kind of error/warning in the import protocol, that may give you a hint.
If nothing helps, create a new sap support case and tell them you are using SAP solutions without modifying anything.
Regards,
Clemens

Automatic Clearing Program not clearing in production run -

Hi All,
I am getting strange problem. I am trying to execute F.13 transaction code and When I run in test run mode its selecting all the relavent POs for GRIR clearing. But when I execute the same in Production run, its not at all picking the POs for GRIR clearing. Can anyone explain me why its not picking in Production run........

Hi Chandra,
you must check the criterion of automatic clearing in the two environnements (test and production). may be there are differences. if it's the case you make changes.
IMG path for the criterion of automatic clearing :
Spro > Financial Accounting (New) > Accounts Receivable and Accounts Payable > Business Transactions > Open Item Clearing > Prepare Automatic Clearing
hope this helps
regards

Why is VI not executable using Labview 7.1 Run-Time Engine?

Hi,
In our Teststand sequence, we have a Labview Action step which is returning an error: "The VI is not executable", along with the error code: -18002.
This error occurs on a Production PC using the L.V. 7.1 Run-Time Engine.
I'm aware of Mass Compiling to ensure all the VI's are the correct version, but this has not resolved the problem.
The software was installed on the production PC using a Teststand created installer, with the Labview Adapter set
correctly to the Run-Time Engine, i.e. not trying to open the Labview Developer Server to execute the step at run time.
Because it's the 1st Labview module to be executed, I added another similar step to run beforehand, i.e. the new simple
Labview code ran first. This executed correctly, but then the next step caused the error above.
The small number of associated sub-vi's are on the target PC, and have been mass compiled.
I've had -18002 errors before, but this is one I cannot cure.
All suggestions gratefully received.
Gary.

Hi Guys,
Regarding this -18002 error when using the Run Time Engine instead of the Development Environment, what is the VI within the step that is failing (in any of the cases you've mentioned) trying to do? Are they built around any toolkits?
In my experiments with a simple VI (with just a user dialogue) using the LabVIEW 7.1 RTE in both TestStand 3.1 and 3.5 this morning, I haven't found any issues
There is a possibility if any of the sub-VIs or toolkits you use contain a Merge Errors.vi, that the Run Time Engine picks up a copy of the VI built for previous versions of the RunTime Engine (due to the order in which the sub-VI directories are scanned), and it cannot convert it.
There are a few solutions for this, the easiest one looks to be to copy the error.llb\Merge Errors.vi for LabVIEW 7.1 into the same directory as the VI you're calling (so TestStand can pick it up easily).
Can you let me know if this solution helps at all? If not, would it be possible to post up any of the code or sequence you're having problems with?
Best wishes,
Mark
Applications Engineer
National Instruments

Automatic Clearing not done in Production Run

Hi,
There is strange case in automatic clearing.
When I am executing the transaction F.13 in test run it is showing a clearing date but when i am executing in production run it is not generating the clearing document.
The message I am getting is as follows:
"SAPMF05A 0131 S    F5 074 5 items were selected
SAPMF05A 0700 S    F5 413 Correct the marked line items
SAPMF05A 0700 S    F5 413 Correct the marked line items
SAPMF05A 0700 S    00 344 No batch input data for screen SAPMF05A 0700"
Please can anyone help me on this.
Thanks,
Srini

Hi,
    Check the field status groups of the accounts involved and also the settings for the document type.
Basically you have a field defined as required, which is not populated by F.13.
You can post a manual clearing to check what field is causing this.
Kind regards

My query is not executing properly after applying patches(bi.7

iam working bi.7 support package 13
after applying patches
my query is not executing properly in production my problem with FI queries
the query is executing properly but ihav created newformula using formulavariable that fields are not getting data in report if i click on currency conversion iam getting popup but currency translation coversion list is not coming and currency type(target currency also not dispalying)
but if i execute same query in development its working properly newformula fields are getting data and currency conversion also working in development
can u please help me in this issure
i hope as soon i will get solutions from bw gurus

That currency conversion problem is solved
i checked TCODE:RSCUR IN PRD its not showing any details
again i checked in dev and moved all currency types dev to production
now its wokring
i hope check with this it will work

Shared Datasource Is Not Valid Error

Using Reporting Services (SQL Server 2008 R2), I have a VS SSRS project with 23 reports, all running off the same Shared Data Source. They all execute in VS. I have deployed the datasource, datasets & reports to server. From the Report
Manager, I can execute all reports except 4, which have the same error:
The report server cannot process the report or shared dataset. The shared data source '22d600c2-a3d5-4178-8a39-d05361607ebd' for the report server or SharePoint site is not valid. Browse to the server or site and select a shared data source. (rsInvalidDataSourceReference)
I have tried the following, without success:
1)verified that the datasource exists in the Data Sources folder, and is Enabled
2) Checked and reset the Shared Datasource to point to the deployed datasource in the Data Sources folder
3) Recreated & redeployed the datasource
4) Deleted the 4 reports on the server and re-deployed
5) Deleted the reports, used Upload instead of Deploy, then set the Shared Datasource to point to the one on the server
6) Verified that the Link column in ReportServer.DataSource is NOT NULL. Actually have the same Link as the other 19 reports. Verified that the GUID in the LinkID exists in Catalog table and is the id for the Datasource.
No matter what I have tried, for some reason, the GUID in these failing reports appear to get set to '22d600c2-a3d5-4178-8a39-d05361607ebd', which does not exist in Catalog table. The other reports never fail, these reports never execute. Anyone
have any ideas?
Victor

As I recall, I went into the Report server db and updated the Catalog table. Open the table and you'll find your reports listed with a link to their datasource (in the DataSource table). I found the 4 reports that failed had a different value
in the LinkID column than the reports that executed, even though they use the same shared datasource.
So I copied the good LinkID value (a GUID) into the 4 reports that failed, and then they ran fine. For some unknown reason, there was an invalid value stuck in the LinkID column which pointed to a datasource that really did not exist.
Go figure.
Victor
Victor Kushdilian

Custom Code not Executing

We implemented SAP 3/1/2010 and have had 3 separate custom programs that have behaved in this same manner. Here is what happens.
1. User runs tcode per usual business process
2. Custom program results are not created. In other words, it appears that the custom program does not execute because the results of the custom program are not created.
3. Rerun same tcode with debug stopper
    a) If the user puts a "debug stopper" in the custom program
    b) the custom code is executed
    c) custom code functions as expected and results are displayed properly
4. remove the stopper
5. Execute tcode and it works properly
So, the custom program is active and is executed (when stopper is there) and functions as expected. However, it does not ALWAYS execute the code (or so it seems from the results that are displayed)
Another work around that we have discovered.
1. User executes tcode and discovers the custom program did not produce expected results
2. User logs off of SAP
3. Logs back on and executes tcode
4. custom program expected results are displayed.
As I said at the beginning, we have experienced this with 3 different custom programs now. I have worked with our Basis team and have not found a solution as to why the custom programs are not executing "all the time".
PLEASE help!

Here are the answers to your questions. Thanks for the quick response.
Custom program = It is code that is executed in a user exit, or is a stand alone program
The 3 different programs are all doing various things. 1) Passing parameters to vertex 2) very complex as it adds pricing conditions and updates forwarding agent partner 3) Stand alone program updates field in BSEG
No security objects are involved in any of the 3 programs.
Yes, this is in the production environment.
No, I have not tried in any other environment because we can not find a situation where the problem always occurs. In other words, I can not duplicate the problem "EVERY TIME" however, when a user encounters the problem it occurs all the time until they do one of our "work arounds" which is to log off SAP or to put a "degug stop" in the program.

Oracle Error - statement handle not executed state

Hello,
A BCA scheduled job has failed and returned with the following error. Does anyone have an idea to fix this error.
Connection or SQL sentence error: (DA0005): [Exception: DBD, ORA-24338: statement handle not executed State: N/A] The following data providers have not been successfully refreshed
Thanks
-Gopi

Please provide more information on what Crystal Reports or Business Objects product you are using. The more details you can provide, the quicker the resolution...
Ludek

Error code returned if the business rules not executed

Recently we found that some Hyperion business rules are not executed during the daily batch file but no error code was returned.
Is there any method to force the return of error code so that we can check the batch result more easier?
Thanks a lot!

For information, we are using the batch file under EAS console directory of Essbase:
\Hyperion\products\Essbase\eas\console\bin\CmdLnLauncher.bat
@echo off
set CPATH=..\lib\CmdLnLauncher.jar
set CPATH=%CPATH%;..\lib\easclientplugin.jar
set CPATH=%CPATH%;..\lib\log4j-1.2.8.jar
set CPATH=%CPATH%;..\lib\framework_common.jar
set CPATH=%CPATH%;..\lib\eas_common.jar
set CPATH=%CPATH%;..\lib\jaxp-api.jar
set CPATH=%CPATH%;..\lib\jdom.jar
set CPATH=%CPATH%;..\lib\dom.jar
set CPATH=%CPATH%;..\lib\xercesImpl.jar
java -DHBR_HOME=..\.. -cp %CPATH% com.hyperion.hbr.cmdlnlauncher.CmdLineLauncher %1 %2 %3 %4 %5 %6

SWL_SUBSTITUTION_DEFINE does not work in production

hi guys,
we have tested to set substitution in qas using FM SWL_SUBSTITUTION_DEFINE and it work. Somehow it does not work in production ? we have checked and set the same setting as if in qas but still user is not able to see the PR in her inbox. pls help

>The assigned agent is meant for classification of SOT
I am not sure that you mean by this? Is there a classification called SOT defined in the system, and the task has been assigned to this classification? If yes, then you need to check the substitution that it is active for this type of tasks (or that it is active for "all" tasks). You should be able to see this also in the sbustitution table (I mean the type of substitution).
Or do you mean that there is some authorisation role called "SOT" in the system, and the possible agents of this task are the users having this role? Then you should be able to see all the users in PFTC under the task.
Regards,
Karri
PS. Remember also to execute transaction SWU_OBUF to refresh the buffers. Maybe it is some strange buffer problem...

DataSource is "NOT EXECUTABLE" in Production

Similar Messages

Maybe you are looking for