Info object in production server

Can we activate an inffoobject in production server ?
how to activate it?
thanks in advance

Hi ramakrishna,
You can activate the info object in production server directly if you have authorizations.
Is it a Standard or Customized,any It's better to activate object in Dev and Transport it to production.
Hope it helps you ..
Reg
Pra

Similar Messages

Issue with Info Object Transport after changing Data Type

Hi Experts,
We have a DSO which is running past 5 years. And recently(3 days back) we added new fields into that DSO. Delta loaded for last three days and new info object (Say XXX) data populated into DSO.
Now the problem is, We identified that, info object data type is not correct. We used data type NUMC instead of CHAR.So Character information is missing for that field.
Example:
Data from ECC: ABC123
Data Loaded to DSO: 123 (Missed character ABC)
So we deleted data from DSO and changed the info object data type in Development system.
And also I have deleted only last three days delta records from DSO and transported my info object to Production. But its giving error as: Info object contains data in DSO".
But that info object field is empty in DSO. I have already deleted last three days delta.
Do I need to Delete all 5 years data from DSO to change the data type of recently added new info object ?
Please give me your solutions and ideas to solve this issue.
Thank you,
Best Regards,
Santhosh

Hi Raman,
Thank you for your answer.
When I changed the data type of info object in Dev, I deleted the content of DSO. And same thing transported to QA as well. Before importing changed info object, I just deleted the content of DSO from QA. So transport done successfully QA.
But in Production we have a history of past 5 years. So I cant delete all contents of DSO.
So just deleted only the delta request's which contains data for that info object(3 days back, we moved that info object(NUMC data type) to production,So last 3 days delta only loaded for that info object). And tried to transport it. But it was failed. I am sure we need to drop all data from DSO, if I am interested to go with same info object.
I have some comments on your first approach,
1. If we delete info objects from Dev DSO and transport to Production will give transport failure, Why because, my previous transports errors clearly saying that info object contains data in DSO . So it wont allow to remove that info object from DSO.
2.We are using same info object technical name in BO Data federator also. So if we change add new info objects again we need to make changes with BO as well. I am thinking this point as my last option if i cant find any other solution.
Thank you.
Best Regards.

Move out Info Provider to other server without transport connection?

Hi All,
Could you share you thought ?
Is there a possibility to move out the info provider design & info object to other server without transport connection ?
The background is our project box will be decommissioned, and unfortunately it's not connected to development box. We've already found how to move out ABAP program, we generate it to XML, than upload it.
How about for info provider itself / info Object ? Is there a possibility to have the same treatment ?
Any thought from all of you ?
If you have the way, appreciate if you can share it to me.
Thanks a lot and have a good day,
Best regards,
Daniel N.

Hi,
From transport side, it is possible. You can create a dummy transport target system, then collect BI objects in request and release it. After release, the exported data is in dir_trans, you can manually copy it to realy target server, put them in dir_trans, and in STMS import Q, select from menu of import external request and import it.

Cannot see Business Objects Repository in SAP production server from Worskpace - SMP 2.3

Hi all,
I have problems with reading RFC from production server, because BOR isn't visible at all in Mobile Workspace. Maybe I do something wrong so let me explain what am trying to accomplish. I need to make applications work on production server. Until now they worked and were tested on development server. Applications are native Android with MBO (SMP 2.3.3). So my guess is that I need to transport RFC functions from development to production, which I did, then to make new connection to production server in workspace and generate MBOs and code from them that will finally replace the old MBO code in Android application. If that is the procedure, then the only problem is that I can't see those RFC in production. My user have sap all privileges and in them S_RFC authorization object so I guess authorization isn't the problem. I also tried to switch the language in workspace connection because last time (on development) that was the problem. Any idea somebody?

Well there is only one mobile server. I don't know exactly how they (client) think it will work but when I say production server I refer to SAP EIS production server.
Anyway the solution to the problem with BOR visibility is this note:
Note 706195 - BAPIs are missing in the component hierarchy display
Thanks Midhun! I will probably have more questions..

Issue in Hierarchy data upload from R/3 for info object Product Hierarchy.

Hi,
I am trying to upload the hierarchy data from R/3 system for Info Object Product Hierarchy.
Insted of business content info objects (0PRODH, 0PRODH1, 0PRODH2, 0PRODH3, 0PRODH4, 0PRODH5, 0PRODH6), we are using customized objects (ZPRODH, ZPRODH1, ZPRODH2, ZPRODH3, ZPRODH4, ZPRODH5, ZPRODH6).
In transfer rules the mapped is as specified below
Fields => Info Objects.
0ZPRODH1 => ZPRODH1
0ZPRODH2 => ZPRODH2
0ZPRODH3 => ZPRODH3
0ZPRODH4 => ZPRODH4
0ZPRODH5 => ZPRODH5
0ZPRODH6 => ZPRODH6
Now, when I schedule the Info Package, it is ending with an errors
"Node characteristic 0PRODH1 is not entered as hierarchy charactersitic for ZPRODH"
"Node characteristic 0PRODH2 is not entered as hierarchy charactersitic for ZPRODH"
"Node characteristic 0PRODH3 is not entered as hierarchy charactersitic for ZPRODH"
"Node characteristic 0PRODH4 is not entered as hierarchy charactersitic for ZPRODH"
"Node characteristic 0PRODH5 is not entered as hierarchy charactersitic for ZPRODH"
"Node characteristic 0PRODH6 is not entered as hierarchy charactersitic for ZPRODH".
when i tried to load by flat file, there is no issues. But, flat file loading is not allowed for us.
Please let me know any possible solution to handle this issue.
Thanks.
Regards,
Patil.

Hi voodi,
Insted of using the info object 0PRODH1, we should use customized info object ZPRODH1 which I added already in the external characteristic in Hierarchy.
Regards,
Patil.

How to find the date when object is moved from quality to production server

Hi Experts,
I am working with BADI ZMM_PUR_REQ_PROC_001-Method Check and BADI ZME_PROCESS_PO_CUST-Method Check.
I need to add a check that a particular logic should be implemented only after this object is moved to the production server.
How can i check the date when an object (in my case this BADI) is moved to the production server?
<Removed by moderator>
Thanks in advance.
Edited by: Vinod Kumar on Aug 1, 2011 10:55 AM

Hi Sakshi,
So your reqt is that the documents created after your Transport implementation date should pass the check and others (old ones) should ignore.
I will recommend, if at all possible, to make all the old documents compatible to your check by doing a separate initial loading /one time activity to avoid this kind of hardcoding.
IF not at all possible to do so, then I think you should better hardcode your Transport req number and fetch date (AS4DATE) from E070 table and only if any entry exists, use that date as your required date. I believe this will be the date of transport imported in the target system.
You can avoid hardcoding Transport number by picking latest transport with respect to your object (BADI) using E071 table, but that will go wrong once you send any future changes in this BADI to Prod, so better to hardcode the transport.
BR,
Diwakar

Transporting object from development to production server

Hi Everyone,
Could you plz tell me how can i transport a object from development server to production serevr if that object is local in production server. And also could u tell me if the transfer structure is replaced if the names are different in both the server???

Could you plz tell me how can i transport a object from development server to production serevr if that object is local in production server.
Case 1: Object is in Prod, but not in Dev. and you want to align the systems through transports.
You will have to send it to D (which could be done by changing transport routes & then following normal transport procedure) & then will have to bring it back with overwrite originals.
Case 2: Object is present both in Prod & Dev.
You can send the transports D->P with Overwrite originals (following the transport procedures).
And also could u tell me if the transfer structure is replaced if the names are different in both the server???
If technical names are different in both the servers, the transfer structure will not be overwritten.

How do you test any SAP objects before a transport to the production server

How do you test any SAP objects before a transport to the production server?

Hi Rama Krishna,
The actual process is develop the object in development system and unit test there with the available data.
Then move it to Quality server where the data will be the actual replica of production and where the integration testing and ened to end testing happens and also the user acceptance testing happens there.
and once everything is found fine there then it is moved to production system.
Award points if this is helpful.
Regards,
Ravi G

How to get List of all activated Info objects in sap BI production system

Hi Experts,
For my requirement I need list of all activated info objects in sap bi production system.
Can any body suggest any thing.

Hi,
Check in the following table, all the below tables are for InfoObejct related only
RSDIOBJ -
Directory of all InfoObjects
RSDIOBJT------ Texts of InfoObjects
RSDIOBJ------- Directory of all InfoObjects
RSDIOBJT----- Texts of InfoObjects
RSDATRNAV------ Navigation Attributes
RSDATRNAVT----- Navigation Attributes
RSDBCHATR------ Master Data Attributes
RSDCHABAS------- Basic Characteristics (for Characteristics,Time Characteristics, and Units)
RSDCHA----
Characteristics Catalog
RSDDPA -
Data Package Characteristic
RSDIOBJCMP----
Dependencies of InfoObjects
RSKYF----
Key Figures
RSDTIM----
Time Characteristics
RSDUNI -
Units
Thanks
Reddy

Transferrring Objects from my Workstation to Production Server

Hi Guys,
I should really thank all you guys for the your help.
I need to know detail steps invloved in Transferrring the Objects from my Workstation to Production Server or testing server.
Thanks
Sid

Hi,
When u create a object and save it, it will ask for the package name to save, then assign one package and then it will ask for the request .
Create the new request. and this request can be released before transporting.
Go to se09 or se10 and then select ur request number and click the release button. then object will be released and is ready to transport to quality.
After that goto STMS and then transport it to qwuality server.
However it will be the work of the basis guy to transport to quality after u have released...
Hope it is needful..
Cheers,
Simha.

Hi,how can i transport objects from one server to other like (Dev To Qty)

Hi Sir/madam,
Can u explain how can i transport objects from one server to other like (Development To Quality To Production).
Regards,
Vishali.

Hi Vishali,
Step 1: Collect all Transports(with Packages) in Transports Tab(RSA1)- CTO
Step 2: Release the subrequests first and then the main request by pressing Truck button
Step 3: STMS or Customized transactions
Object Collection In Transports:
The respective Transports should have the following objects:
1. Base Objects -
a. Info Area
b. Info object catalogs
c. Info Objects
2. Info Providers u2013
a. Info Cubes
b. Multi Providers
c. Info Sets
d. Data Store Objects
e. Info Cube Aggregates
3. Transfer Rules u2013
a. Application Components
b. Communication Structure
c. Data Source replica
d. Info Packages
e. Transfer Rules
f. Transformations
g. Info Source Transaction data
h. Transfer Structure
i. Data sources (Active version)
j. Routines & BW Formulas used in the Transfer routines
k. Extract Structures
l. (Note) If the transfer structures and related objects are being transferred without preceding
Base Objects transport (e.g. while fixing an error) it is safer to transport the related Info
Objects as well.
4. Update Rules u2013
a. Update rules
b. Routines and formulas used in Update rules
c. DTPs
5. Process Chains u2013
a. Process Chains
b. Process Chain Starter
c. Process Variants
d. Event u2013 Administration Chains
6. Report Objects u2013
a. Reports
b. Report Objects
c. Web Templates
Regards,
Suman

Urgent::::Data is not loaded for a perticular info object in ods

Hi All,
We have loaded data into an ODS( 0PRC_DS01) in development server. It was successfully loaded into it all info objects.Reports were working well.
When we transported it to production, data loading was taking longggg time (15000 for 9 hours).So, we have done two things to improve the loading speed.
1) we have created an index based on the fields in the where clause RCLNT,RLDNR,RYEAR, DOCNR, POPER in JVSO1 table.
(JVSO1 is an R/3 table from where key data coming to datasource 0EN_JVA_2.)
2)We have updated the optmizer statistics.
Now the problem is, data is not loaded to one perticular info object JOINT VENTURE PARTNER in dso. Which was loaded successfully in development.
Please help us........We will assign points for helpful answers

Hi Chek in the transfer and update rules whether u mapped the fields with target and also check whether u have routine. and check whether the data is coming for that object from the source.
Khaja

Organizational structure not found in production server need advice

HELLO
suddenly posting date was go back to 2008 then our fi consultant get it back to current date but in hr module complit organizational structure was not in PPOM_OLD but positions are in the position screen but not showing the org unit abbr respective positions .
org unit abbr was blank. And when I search the org unit with the object key massage display "object not found"
so kindly give me solution that how can that structure recovered to production Server?

Hi Siba,
hope u r doing good.
Go to table T778P and check whether plan version 01 is set to active and current.
Also try to check with Tcodes : PPOME or PP01 .
Dont worry your Org Stru wont go anywer, Pls scout forum for more clues.
Re: Plan version and org structure
check this thread for more info on Plan versions
Regards
Rohit.S

LOGO IS NOT COMING IN SCRIPT IN PRODUCTION SERVER ONLY

Dear all,
i had modify a std script for payment advice for FI module. my problem is that the company logo is not coming in form after execting it from tcode f-58 in production server only.
i checked that graphics object in se78 in prod.sever , it is present there. the thing is that the logo is coming in the form when i executing it from development sever. can any body tell where is the problem.
thanks
Banaja

Hi,
May be you have changed the form in DEV and in PRD your print program is still calling the std form and not the new (z-form).
Might be a good idea to check that in t-code NACE !
Let us know if this solves your problem.
Regards
Hrishi

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
SELECT *
FROM mkpf
INTO CORRESPONDING FIELDS OF TABLE mkpf_itab
FOR ALL ENTRIES IN mseg_itab
WHERE mblnr EQ mseg_itab-mblnr.
in this your internal table contains only 2 fields
mblnr LIKE mkpf-mblnr, "Number of Material Document
bldat LIKE mkpf-bldat, "Document Date in Document , 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

Info object in production server

Similar Messages

Maybe you are looking for