Re-transport the transport request in Quality server after System refresh

Hi
Users are moving the transport requests in NQA (quality server) using STMS tcode and Basis team is moving the trasnport requests using TP command in operating system level.
There are some transport requests that are released and are moved only to NQA server but not in Production server.
After the NQA refresh from Production server, we need to re-create the trasnport route for NQA server
in NQA using SE06 and STMS.
Now users want to re-transport the requests again in NQA server that was moved to NQA before the system copy but they are not able to make it. In the transport queue, users are able to see their transport requests but they are not able to re-transport.
When basis team try to move the same transport requests using TP command in operating system level, it failed with error:
- "Transport request is not in buffer".
- x2n0v2:nqaadm 14> transport250_NQAu126 908807
/usr/sap/trans/NDV/cofiles/K908807.NDV
is this the correct cofile ?y
cofile is K908807.NDV
source system is NDV
transport type is K
transport name is NDVK908807
Renamed to K908807.NDV.INTRANSIT on dbcindv
Datafile copied to dbcinqa
Cofile copied to dbcinqa
-rw-rw-r--   1 nqaadm     sapsys       25606 Oct 29 11:13 /usr/sap/trans/NQA/data/R908807.NDV
-rw-rw-r--   1 ndvadm     sapsys       25606 Oct 29 11:13 /usr/sap/trans/NDV/data/R908807.NDV
-rw-rw-r--   1 nqaadm     sapsys         678 Dec 1 19:05 /usr/sap/trans/NQA/cofiles/K908807.NDV
-rw-rw-r--   1 ndvadm     sapsys         678 Dec 1 19:05 /usr/sap/trans/NDV/cofiles/K908807.NDV.INTRANSIT
Please compare the files before proceeding
Do you wish to continue the import?y
tp addtobuffer NDVK908807 NQA pf=TP_DOMAIN_NDV.PFL
This is tp version 305.13.25 (release 46D) for ANY database
Addtobuffer failed for NDVK908807.
Cofile not existent or corrupted (datafile exists).
If source system is available you may try to reconstruct
the cofile using the command "createinfo".
We used the following method to re-transport the requests to NQA server:
"STMS --> Request -->Delete (the request number)" method delete the transport request from transport queue and from the cofiles/data directory of the operating system and then " STMS --> extra-> other request-> add" allow us to put the transport request back to transport queue in NQA server. Once the transport requests are in queue, we can re-transport all of them one by one or in group.
Question: Is it the right way to re-transport the request in NQA (first delete if from transport queue and then add and then re-import in NQA server).
Id there is any other way to re-transport the requests, pls suggest us.
Thanks
Amar

No cross posting
Read the "Rules of Engagement"
Regards
Juan

Similar Messages

Re-transport the transport request to NQA server after system refresh

Hi
Users are moving the transport requests in NQA (quality server) using STMS tcode and Basis team is moving the trasnport requests using TP command in operating system level.
There are some transport requests that are released and are moved only to NQA server but not in Production server.
After the NQA refresh from Production server, we need to re-create the trasnport route for NQA server
in NQA using SE06 and STMS.
Now users want to re-transport the requests again in NQA server that was moved to NQA before the system copy but they are not able to make it. In the transport queue, users are able to see their transport requests but they are not able to re-transport.
When basis team try to move the same transport requests using TP command in operating system level, it failed with error:
- "Transport request is not in buffer".
- x2n0v2:nqaadm 14> transport250_NQAu126 908807
/usr/sap/trans/NDV/cofiles/K908807.NDV
is this the correct cofile ?y
cofile is K908807.NDV
source system is NDV
transport type is K
transport name is NDVK908807
Renamed to K908807.NDV.INTRANSIT on dbcindv
Datafile copied to dbcinqa
Cofile copied to dbcinqa
-rw-rw-r--   1 nqaadm     sapsys       25606 Oct 29 11:13 /usr/sap/trans/NQA/data/R908807.NDV
-rw-rw-r--   1 ndvadm     sapsys       25606 Oct 29 11:13 /usr/sap/trans/NDV/data/R908807.NDV
-rw-rw-r--   1 nqaadm     sapsys         678 Dec 1 19:05 /usr/sap/trans/NQA/cofiles/K908807.NDV
-rw-rw-r--   1 ndvadm     sapsys         678 Dec 1 19:05 /usr/sap/trans/NDV/cofiles/K908807.NDV.INTRANSIT
Please compare the files before proceeding
Do you wish to continue the import?y
tp addtobuffer NDVK908807 NQA pf=TP_DOMAIN_NDV.PFL
This is tp version 305.13.25 (release 46D) for ANY database
Addtobuffer failed for NDVK908807.
Cofile not existent or corrupted (datafile exists).
If source system is available you may try to reconstruct
the cofile using the command "createinfo".
We used the following method to re-transport the requests to NQA server:
"STMS --> Request -->Delete (the request number)" method delete the transport request from transport queue and from the cofiles/data directory of the operating system and then " STMS --> extra-> other request-> add" allow us to put the transport request back to transport queue in NQA server. Once the transport requests are in queue, we can re-transport all of them one by one or in group.
Question: Is it the right way to re-transport the request in NQA (first delete if from transport queue and then add and then re-import in NQA server).
Id there is any other way to re-transport the requests, pls suggest us.
Thanks
Amar

Amar,
Depending on how many tarnsports you have and also if this is one time, what you can do is ask Basis guys to write a small script which adds to the buffer to your NQA system.
Steps:
1) under /usr/sap/trans/buffer rename the NQA buffer file.
2) create a new empty file NQA (make sure permissions are identical)
3) Provide the list of transports and ask Basis team to put it in a file at Unix level
4) Run a script which will add to the buffer from the source file.
5) From STMS refresh the NQA queue and you should see all the transports ready for import.
Hope this helps.
Thanks,
Naveed
Edited by: Naveed Qureshi on Dec 4, 2008 8:52 AM

How to retrieve the Sapscript layout changes for a particular Transport request in development server after this Transport request so many requests created ?

Dear Abapers,
I request the Abapers kindly reply for this blog
I want to retrieve the sapscript layout changes for a particular transport request in development server after that many transport request created and moved to quality ?
I checked in SE03 transaction the transport request was there. But I want to retrieve the existing transport request which is not moved to Quality?
Is it possible to retrieve the existing transport request in development which is not moved to quality ?
Like how we retrieving the programs using versions in development server, In the same way I want to retrieve the sapscript layout in development server ?
Thanks & Regards
Muzeebur Rahiman.S

Hi,
There is no version management for SapScript or Smartforms .
When you write "transport request in development which is not moved to quality" - was the transport ever released and exported from the development system? If yes, and if the "Transport files" are still available in "Transport directory" (or if the transport files were backed up and could be retrieved), the transport could be imported again. If the TR was not exported, you are out of luck, I believe...
I would not recommend you do it on your own even if you happen to have enough authorizations (consult with Basis and/or Transport Admin, if you have one in your organization). I would not recommend that it's imported on a development system or QA system, even if the transport contains no other objects - only the SapScript form in question. Import it on a "sand-box" that gets overwritten by system copy from time to time... Once the transport is imported, you should have the old version of SapScript in that system and could analyse the changes and perform manual merge.
cheers
Jānis

Transport request in quality server

Hi everyone..never mind if this is not the correct place to post this question..i have the access to ECC QUALITY SERVER..i tried to generate the datasources in ECC Quality server..it has given PROMPT FOR LOCALWORKBENCH REQUEST pop-up window
when i look for the available requests through F4(input values)..there are no input values..
Dont we have the possibility to activate datasources in quality server?why so?and if anybody knows details about development,quality and production server could you please give me a broad explanation??im confused with these three types of servers and how they work!!
Thank you very much in advance for any help,
Edited by: yarpath on Sep 22, 2011 11:21 AM

Hi ,
Along with provided details Some info about server .
In SAP Landscape we have a server system called SAP architecture
DEV, QAS and PROD.
- DEV would have multiple clients.
190- Sandbox -Sandbox doesn't affect the other servers or clients its standalone system
100- Golden- dev and changes transferred to next level via transports it contains all configuration and master data .So all the configuration settings are done in golden clients and then moved to other clients. Hence this client acts as a master copy for all settings to be done so called "Golden Client"..
180- Unit Test- if configures then Transports from golden client will come here .
- QAS may again have mutiple clients
300- Integration Test
700 to 710 Training.
- PROD usually have one client
this depends on how is the client's business scenario.
Request flow like
DEVELOPMENT -> QUALITY -> PRODUCTION
DEVELOPMENT : where developer create new objects and flow or change existing one .
QUALITY : The objects moved from Dev tested as it has large amount of data and usually a copy of production so new development get tested with real time data and any bugs etc found can be fixed back in dev and get transported again .
PRODUCTION : Day to day business data is present here coming from different systems (R/3 ,flat file ,NON SAP system etc).
--In quality or producation you cannot see your transport request and it will not allow you to change object .
--Usually we have only access to create DTP ,Process chain ,Program etc in Production but we cannot change transfromation etc as the flow can not be disturbed .
--To see the status of your objects in any system which are moved via transport you need to see logs in Dev system .
--this will also tell you which systems are connected to your dev system .
Hopw this will be helpful .
Regards,
Jaya Tiwari

Steps for transporting the created request

hi,
sap gurus,
kindly explain the configuration steps for
how we will transport a created request
from one server to another
regards,
balaji.t
09990019711.

Transport Request is generated in following scenarios:
1. Customizing Request - When doing or changing some customization.
2. WorkBench Request - When configuration is cross-client. Eg Generating new Table, making changes in access sequence, Abap development, etc.
Transport Request is released through SE10, to be transported to Quality & production server.
Configuration of Transport Request System is configured by Basis consultant. Basis Consultant is also responsible for transporting the Transport request from Development server to Quality & Production.
Transport request is not generated for Master Data. For eg: Customer Master, Material Master, price master, etc.
Benefit of Transport Request:
SAP Landscape normally has 3- Tier system:
Development Server - Where customization takes place. Transport request is generated at this level & then first transported to Quality server for testing whether it meets the requirement or not. Once the requirement is met in Quality server then Request is transported from Development Server to Production Server (Actual / Live System)
Quality Server - Mainly useful for testing.
Production Server Actual / Live server, where the real transactions are created & posted.
Regards,
Rajesh Banka
Reward Points if Helpful.

Replication of Datsources after Transporting the BI request.

Hi,
I am transporting the request from BI DEV to BI PROD. While transporting the request, do i need to replicate the datasources before transporting the request. Do i need to create Source systems before transporting the BI requests from DEV to Production..Pls Suggest.
Thanks,
Siva.

Hi Siva,
If there is any changes done in data source. If yes then you need to transport the data source in source system and then replicate itin production system and then Transport your BW request.
What do you mean by create source system, it might already be created you do not have to create it. If source system is not existing in your BI then you need to create it by creating RFC connection.
Regards,
Kams

Can not import requests in Quality Server

Dear Gurus,
Please find below logs and let me know where error is coming.
We configure some changes and released it to quality server but I am not able to transfer requests in Quality Server and tp system log is as per below.
When I transfer requests it goes in continuously loop mode endlessly. I delete those requests from import monitor queue then restarted it but same results.
Please guide me what to do......
System Log Entries
START imp single DIQ 20140303102340 INSERV01 sapdnl10 20140303102339554
INFO TBATG CONVERSION OF DIQ N not needed INSERV01 sapdnl10 20140303102339554
START MOVE NAMETABS DIQ 6 20140303102342 INSERV01 sapdnl10 20140303102339554
START tp_getprots DIQ P 20140303102345 INSERV01 sapdnl10 20140303102339554
START imp single DIQ 20140303102713 INSERV01 sapdnl10 20140303102712936
INFO TBATG CONVERSION OF DIQ N not needed INSERV01 sapdnl10 20140303102712936
START tp_getprots DIQ P 20140303102713 INSERV01 sapdnl10 20140303102712936
STOP tp_getprots DIQ P 20140303102849 INSERV01 sapdnl10 20140303102712936
START MOVE NAMETABS DIQ 6 20140303102849 INSERV01 sapdnl10 20140303102712936
START tp_getprots DIQ P 20140303102849 INSERV01 sapdnl10 20140303102712936
STOP tp_getprots DIQ P 20140303103000 INSERV01 sapdnl10 20140303102339554
STOP MOVE NAMETABS DIQ 6 20140303103000 INSERV01 sapdnl10 20140303102339554
START MAIN IMPORT DIQ I 20140303103000 INSERV01 sapdnl10 20140303102339554
STOP tp_getprots DIQ P 20140303103004 INSERV01 sapdnl10 20140303102712936
STOP MOVE NAMETABS DIQ 6 20140303103004 INSERV01 sapdnl10 20140303102712936
START MAIN IMPORT DIQ I 20140303103004 INSERV01 sapdnl10 20140303102712936
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (10), I'm waiting 4 sec (20140303103028). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (10), I'm waiting 4 sec (20140303103032). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (20), I'm waiting 1 sec (20140303103052). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (20), I'm waiting 1 sec (20140303103056). My name: pid 13240
START imp single DIQ 20140303103059 INSERV01 sapdnl10 20140303103059141
INFO TBATG CONVERSION OF DIQ N not needed INSERV01 sapdnl10 20140303103059141
START MOVE NAMETABS DIQ 6 20140303103059 INSERV01 sapdnl10 20140303103059141
START tp_getprots DIQ P 20140303103059 INSERV01 sapdnl10 20140303103059141
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (30), I'm waiting 4 sec (20140303103116). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (30), I'm waiting 4 sec (20140303103120). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (40), I'm waiting 2 sec (20140303103147). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (40), I'm waiting 2 sec (20140303103151). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (50), I'm waiting 2 sec (20140303103222). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (50), I'm waiting 2 sec (20140303103226). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (60), I'm waiting 1 sec (20140303103258). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (60), I'm waiting 1 sec (20140303103302). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (70), I'm waiting 4 sec (20140303103320). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (70), I'm waiting 4 sec (20140303103324). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (80), I'm waiting 1 sec (20140303103357). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (80), I'm waiting 1 sec (20140303103401). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (90), I'm waiting 5 sec (20140303103422). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (90), I'm waiting 5 sec (20140303103426). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (100), I'm waiting 3 sec (20140303103454). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (100), I'm waiting 3 sec (20140303103458). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (110), I'm waiting 4 sec (20140303103524). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (110), I'm waiting 4 sec (20140303103529). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (120), I'm waiting 3 sec (20140303103553). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (120), I'm waiting 3 sec (20140303103558). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (130), I'm waiting 2 sec (20140303103624). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (130), I'm waiting 2 sec (20140303103629). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (140), I'm waiting 2 sec (20140303103656). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (140), I'm waiting 2 sec (20140303103701). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (150), I'm waiting 3 sec (20140303103726). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (150), I'm waiting 3 sec (20140303103731). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (160), I'm waiting 1 sec (20140303103758). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (160), I'm waiting 1 sec (20140303103803). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (170), I'm waiting 4 sec (20140303103824). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (170), I'm waiting 4 sec (20140303103829). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (180), I'm waiting 4 sec (20140303103857). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (180), I'm waiting 4 sec (20140303103902). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (190), I'm waiting 1 sec (20140303103922). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (190), I'm waiting 1 sec (20140303103927). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (200), I'm waiting 2 sec (20140303103948). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (200), I'm waiting 2 sec (20140303103953). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (210), I'm waiting 5 sec (20140303104018). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (210), I'm waiting 5 sec (20140303104023). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (220), I'm waiting 3 sec (20140303104046). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (220), I'm waiting 3 sec (20140303104051). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (230), I'm waiting 4 sec (20140303104118). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (230), I'm waiting 4 sec (20140303104122). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (240), I'm waiting 2 sec (20140303104156). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (240), I'm waiting 2 sec (20140303104200). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (250), I'm waiting 2 sec (20140303104225). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (250), I'm waiting 2 sec (20140303104229). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (260), I'm waiting 5 sec (20140303104256). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (260), I'm waiting 5 sec (20140303104300). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (270), I'm waiting 1 sec (20140303104331). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (270), I'm waiting 1 sec (20140303104335). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (280), I'm waiting 5 sec (20140303104356). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (280), I'm waiting 5 sec (20140303104400). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (290), I'm waiting 2 sec (20140303104425). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (290), I'm waiting 2 sec (20140303104429). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (300), I'm waiting 3 sec (20140303104459). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (300), I'm waiting 3 sec (20140303104503). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (310), I'm waiting 2 sec (20140303104529). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (310), I'm waiting 2 sec (20140303104533). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (320), I'm waiting 2 sec (20140303104559). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (320), I'm waiting 2 sec (20140303104603). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (330), I'm waiting 3 sec (20140303104629). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (330), I'm waiting 3 sec (20140303104633). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (340), I'm waiting 2 sec (20140303104700). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (340), I'm waiting 2 sec (20140303104704). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (350), I'm waiting 5 sec (20140303104725). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (350), I'm waiting 5 sec (20140303104729). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (360), I'm waiting 1 sec (20140303104759). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (360), I'm waiting 1 sec (20140303104803). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (370), I'm waiting 4 sec (20140303104828). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (370), I'm waiting 4 sec (20140303104832). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (380), I'm waiting 3 sec (20140303104858). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (380), I'm waiting 3 sec (20140303104902). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (390), I'm waiting 4 sec (20140303104922). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (390), I'm waiting 4 sec (20140303104926). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (400), I'm waiting 2 sec (20140303104959). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (400), I'm waiting 2 sec (20140303105003). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (410), I'm waiting 2 sec (20140303105025). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (410), I'm waiting 2 sec (20140303105029). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (420), I'm waiting 3 sec (20140303105046). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (420), I'm waiting 3 sec (20140303105050). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (430), I'm waiting 5 sec (20140303105119). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (430), I'm waiting 5 sec (20140303105124). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (440), I'm waiting 5 sec (20140303105151). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (440), I'm waiting 5 sec (20140303105156). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (450), I'm waiting 4 sec (20140303105217).

Hi Irin,
Just rename this file \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ
and start the import again.
Hope this helps.
Regards,
Deepak Kori

How to delete the duplicate requests in a cube after compression.

Hi experts,
1. How to delete the duplicate requests in a cube after compression.?
2. How to show a charaterstics and a keyfigure side by side in a bex query output?
Regards,
Nishuv.

Hi,
You cannot delete the request as its compressed as all the data would have been moved to E table ..
If you have the double records you may use the selective deletion .
Check this thread ..
How to delete duplicate data from compressed requests?
Regards,
shikha

Change the description of the change request number" in SE10 after release

Hi All
Is there way to change the
"description of the change request number" in SE10
after releasing the change request number?
appreciate your feedback
Thanks you
Iver

Hello
I do not know a way to do it in se10 but a simple program could do the trick.
Include the following code in your program.
update e07t set as4text = 'your new description'
where trkorr = your_cr and langu = 'E'.
Of course you will have to wrestle with the 'moral issue' of directly updating SAP delivered tables
Regards
Greg Kern.

HOW TO TRANSPORT THE STANDARD TEXT FROM ONE SERVER TO ANOTHER?

After creating the standard text in SO10 transaction
it will not ask for any transport request no while saving ,
i want to transport the standard text from development to test server.
how can we do that?

Hi Riaz,
To transport a Standard Text through a transport request , you need to attach the standard text through the transaction RSTXTRAN.
After executing the report RSTXTRAN , you can enter first the task name then the Object as TEXT , then the name of the standard text , ID as ST, then the language as EN or something else .then execute.
you cannot attach a standard text to an unassigned task.Firat you have to either activate a smartform or a script with that task then only you have to attach a standard text.
I think your query is almost answered .
Reward if you please.
Thanks & regards,
Ram

Problem in quality server after transport

HI,
Yesterday i have transferred a function group from development to quality. It's transorted successfully .All the function module under this group are active. but the status function group shows 'Inactive' because in main program the include is not active. when i go for a syntax check it is correct. while activating it it says <b> "the object is in the worklist of D_tal"</b>
N.B. It was earlier transported to quality . it was working fine in quality. later somebody has deleted some function module from quality and also some unicode check issue was there in quality . so we corrected it in development and created a new Transport request for that function group and transported it.
Why that error "the object is in the worklist of D_tal" is coming.
thanks&regards
sandeep

Hi,
When you transport request into Quality, there will be an option to overwrite existing (Force into system) objects in that system. Ask you BASIS to do the same.
Caution: Transport request objects belongs to that Function group only. It should not impact any other object.
Regards,
Govind.

Error in transporting the zscript form to quality.

Hi Friends ,
i copied standered script to z script by name ZF110_CHECK_PRIN . i modified the z script form .i have a written a program in se38 for printing of multiple cheques , i call this form in my program everything was going well in developement iam able to print in development , when i transport this form to quality it is in inactive version , and giving this error description.
Form ZF110_CHECK_PRIN language EN is not active and has no errors
Message no. TD422
Diagnosis
The form assigned to the document is not active.
System Response
The form will not be formatted.
Procedure
Please check in the SAPscript form maintenance transaction and see whether the form exists and, if this is the case, whether an active version exists. An active version does not exist if you find the entry New in the status line of the form maintenance transaction.
If the form you selected does not exist, either assign a form that already exists to your document, or create a new form which can be used for your document once it has been generated.
You activate a new form using the function Generate.
It is also possible for an error to occur even if your form has the status 'active'. This error message is the result of extended checks, that were not available the last time that your form was activated. In this case, please select the menu option Form -> Check -> Definition and complete the actions specified in the resulting message.
A typical error: A text element in window ... does not contain a name. In this case, display the text elements and ensure that each text element (format column /E) has a name so that it can be addressed by the print program. The default text element (at the beginning, no /E) is addressed and processed automatically. Never enter /E without a name following it.

Hi,
I presume you can not activate the form directly in Quality. If that is the case then
In development create another request for the same form may be by keying in some remarks somewhere or even a single '.' will do. Activate the form & transport it agian to quality. That should sort out your problem.
I hope this helps,
Regards
Raju chitale

Transporting ODS from Developement to Quality server

Hi,
In Quality server I am haveing ODS with out one navigational attribute included in it but it contains data.same is avaliable in development with navigation attribute object included in it.Now we want to transport this ODS from development to Quality.Kindly let us know if we need to delete the data from ODS in quality before moving this ods which is in the delevopment.Technical name for both ods is same.
Regards,

Hi,
You don't have to delete the data. The transport will work fine. But, the more data you have, the longer the transport will take.
Cheers,
Kedar

Steps to transport the forecast profiles from development server to the pro

Hello All,
We have a scenario wherein we need to transport forecast profiles from APO development server to the APO production sever.
Can anyone suggest me proper steps to include the forecast profiles into the transport request.
Thanks in advance.
Regards,
Jacky.

Hi Sujay ,
Thanks again.
I did check the transaction mentioned by you. But it din't help in my scenario.
I got the sloution for my problem,
we have two tables for forecast profiles, i,e /SAPAPO/DP440G and /SAPAPO/DP440P (these gets updates as and when we create a forecast profiles ) ,
we have to add the entries from this table for the particular forecast profile into the transport request and then we have to transport those requesets , then the profiles would be transported accordingly.
Anyways thanks for replying.. i am giving you points for helping me..:-)
Regards,
Jacky Jain.

Dump is coming after Moving the request to Quality server.

Dear All,
Dump is coming in a ABAP code after moving the same to quality server.
Kindly refer the attached screenshot.
Kindly suggest.
Thanks and Regards
Jai

see the below code,
I have changed the value of l_age1 TYPE bsid-dmbtr to l_age1 TYPE p LENGTH 10 DECIMALS 2.
*& Report ZFIRDEBAGEING
* 1. Program Name:ZFIRDEBAGEING             2. Creation Dt:18/03/2013 *
* 3. Module Name :FI                        4. Modified Dt:2/04/2013 *
* 5. Developer Name: Kallol Chakrabarty     6. Modified By:           *
* 7.Background / Online :Online             8. Trans Code : ZCAGE      *
* 9. Frequency : Regular    *
* Request Number :            - Created                                *
* Remarks : Customer Ageing Report                                     *
REPORT zfirdebageing.
TYPE-POOLS : slis.
TABLES: bsid,bseg.
TYPES : BEGIN OF tt_bsid,
          belnr TYPE belnr_d,
          gjahr TYPE gjahr,
          bukrs TYPE bukrs,
          dmbtr TYPE dmbtr,
          kunnr TYPE kunnr,
          budat TYPE budat,
          zfbdt TYPE dzfbdt,
          zterm TYPE dzterm,
          zbd1t TYPE dzbd1t,
          shkzg TYPE shkzg,
        END OF tt_bsid,
        BEGIN OF tt_bseg,
          belnr TYPE belnr_d,
          gjahr TYPE gjahr,
          bukrs TYPE bukrs,
          werks TYPE werks_d,
          prctr TYPE prctr,
          segment TYPE fb_segment,
        END OF tt_bseg,
        BEGIN OF tt_faglseg,
          langu TYPE spras,
          segment TYPE fb_segment,
          name TYPE text50,
        END OF tt_faglseg,
        BEGIN OF tt_cepct,
          spras TYPE spras,
          prctr TYPE prctr,
          ltext TYPE ltext,
        END OF tt_cepct,
        BEGIN OF tt_final,
          kunnr TYPE kunnr,
          segment TYPE fb_segment,
          name TYPE text50,
          prctr TYPE prctr,
          ltext TYPE ltext,
          name1 TYPE name1_gp,
          ort01 TYPE ort01_gp,
          age1 TYPE dmbtr,
          age2 TYPE dmbtr,
          age3 TYPE dmbtr,
          age4 TYPE dmbtr,
          age5 TYPE dmbtr,
          age6 TYPE dmbtr,
          age7 TYPE dmbtr,
          total TYPE dmbtr,
          total1 TYPE dmbtr,
          total2 TYPE dmbtr,
          zfbdt TYPE dzfbdt,
          zterm TYPE dzterm,
          zbd1t TYPE dzbd1t,
          budat TYPE budat,
        END OF tt_final,
        BEGIN OF tt_kna1,
          kunnr TYPE kunnr,
          name1 TYPE name1_gp,
          ort01 TYPE ort01_gp,
        END OF tt_kna1.
DATA : wa_bsid TYPE tt_bsid,
        it_bsid TYPE TABLE OF tt_bsid,
        wa_bseg TYPE tt_bseg,
        it_bseg TYPE TABLE OF tt_bseg,
"       wa_tmp1 TYPE tt_bseg, "Commented by ++KC 18.03.2013 after extended check
        it_tmp1 TYPE TABLE OF tt_bseg,
        wa_faglseg TYPE tt_faglseg,
        it_faglseg TYPE TABLE OF tt_faglseg,
        wa_cepct TYPE tt_cepct,
        it_cepct TYPE TABLE OF tt_cepct,
        it_tmp TYPE TABLE OF tt_bsid,
        wa_final TYPE tt_final,
        it_final TYPE TABLE OF tt_final,
        wa_final1 TYPE tt_final,
        it_final1 TYPE TABLE OF tt_final,
        wa_kna1 TYPE tt_kna1,
        it_kna1 TYPE TABLE OF tt_kna1.
*& ALV Data Declaration                                                *
DATA: it_fieldcat TYPE slis_t_fieldcat_alv,
       wa_fieldcat TYPE slis_fieldcat_alv,
       is_layout   TYPE slis_layout_alv,
       wa_event    TYPE slis_alv_event,
       it_event    TYPE slis_t_event.
SELECTION-SCREEN: BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS : s_kunnr FOR bsid-kunnr.
PARAMETERS : p_bukrs TYPE bseg-bukrs OBLIGATORY,
                    p_dateon TYPE bsid-budat DEFAULT sy-datum OBLIGATORY.
SELECTION-SCREEN : END OF BLOCK b1.
SELECTION-SCREEN: BEGIN OF BLOCK b2 WITH FRAME TITLE text-003.
SELECT-OPTIONS : s_werks FOR bseg-werks,
                    s_sgmnt   FOR bseg-segment,
                    s_prctr   FOR bseg-prctr.
SELECT-OPTIONS : s_umskz FOR bsid-umskz.
SELECTION-SCREEN : END OF BLOCK b2.
DATA: v_days TYPE string,
       v_date1 TYPE bsid-budat,
       v_date2 TYPE bsid-budat,
       v_date3 TYPE bsid-budat,
       v_date4 TYPE bsik-budat,
       v_date5 TYPE bsik-budat,
       v_date6 TYPE bsik-budat,
       v_date7 TYPE bsik-budat,
*     l_age1 TYPE bsid-budat,
*     l_age2 TYPE bsid-dmbtr,
*     l_age3 TYPE bsid-dmbtr,
*     l_age4 TYPE bsid-dmbtr,
*     l_age5 TYPE bsid-dmbtr,
*     l_age6 TYPE bsid-dmbtr,
*     l_age7 TYPE bsid-dmbtr,
       l_age1 TYPE p LENGTH 10 DECIMALS 2,
       l_age2 TYPE p LENGTH 10 DECIMALS 2,
       l_age3 TYPE p LENGTH 10 DECIMALS 2,
       l_age4 TYPE p LENGTH 10 DECIMALS 2,
       l_age5 TYPE p LENGTH 10 DECIMALS 2,
       l_age6 TYPE p LENGTH 10 DECIMALS 2,
       l_age7 TYPE p LENGTH 10 DECIMALS 2.
CONSTANTS : v_age1(4) TYPE c VALUE 15 ,
             v_age2(4)    TYPE c VALUE 30,
             v_age3(4)    TYPE c VALUE 45,
             v_age4(4)    TYPE c VALUE 90,
             v_age5(4)    TYPE c VALUE 180,
             v_age6(4)    TYPE c VALUE 360,
             v_age7(4)    TYPE c VALUE 360.
INITIALIZATION.
   sy-title = 'CUSTOMER AGEING'.
*--------------- S-T-A-R-T O-F S-E-L-E-C-T-I-O-N ----------------------*
START-OF-SELECTION.
   PERFORM get_data.
   PERFORM process_data.
   PERFORM alv_display.
*&      Form GET_DATA
*       text
* --> p1        text
* <-- p2        text
FORM get_data .
   SELECT belnr
           gjahr
           bukrs
           dmbtr
           kunnr
           budat
           zfbdt
           zterm
           zbd1t
           shkzg
           FROM bsid INTO TABLE it_bsid
           WHERE kunnr IN s_kunnr
           AND bukrs = p_bukrs
*          AND zfbdt <= p_dateon
               AND budat <= p_dateon
           AND umskz IN s_umskz.
   SELECT      belnr
               gjahr
               bukrs
               dmbtr
               kunnr
               budat
               zfbdt
               zterm
               zbd1t
               shkzg
               FROM bsad APPENDING CORRESPONDING FIELDS OF TABLE it_bsid
               WHERE kunnr IN s_kunnr
               AND bukrs = p_bukrs
               AND augdt > p_dateon
               AND umskz IN s_umskz.
   IF it_bsid[] IS NOT INITIAL.
     it_tmp[] = it_bsid[].
     DELETE ADJACENT DUPLICATES FROM it_tmp COMPARING kunnr.
     SELECT kunnr
            name1
            ort01 FROM kna1 INTO TABLE it_kna1
                                  FOR ALL ENTRIES IN it_tmp
                                  WHERE kunnr = it_tmp-kunnr.
     SELECT belnr
            gjahr
            bukrs
            werks
            prctr
            segment
            FROM bseg INTO TABLE it_bseg
                      FOR ALL ENTRIES IN it_bsid
                      WHERE belnr = it_bsid-belnr
                      AND   gjahr = it_bsid-gjahr
                      AND   werks IN s_werks
                      AND   prctr IN s_prctr
                      AND   segment IN s_sgmnt
                      AND umskz IN s_umskz.
     IF it_bseg[] IS NOT INITIAL.
       it_tmp1[] = it_bseg[].
       SORT it_tmp1 BY segment.
       DELETE ADJACENT DUPLICATES FROM it_tmp1 COMPARING segment.
       SELECT langu
              segment
              name
              FROM fagl_segmt INTO TABLE it_faglseg
                              FOR ALL ENTRIES IN it_tmp1
                              WHERE langu = 'EN'
                              AND segment = it_tmp1-segment.
       REFRESH it_tmp1.
       it_tmp1[] = it_bseg[].
       SORT it_tmp1 BY prctr.
       DELETE ADJACENT DUPLICATES FROM it_tmp1 COMPARING prctr.
       SELECT spras
               prctr
               ltext
               FROM cepct INTO TABLE it_cepct
                          FOR ALL ENTRIES IN it_tmp1
                          WHERE spras = 'EN'
                          AND   prctr = it_tmp1-prctr.
     ENDIF.
   ENDIF.
ENDFORM. " GET_DATA
*&      Form PROCESS_DATA
*       text
* --> p1        text
* <-- p2        text
FORM process_data .
   v_date1 = p_dateon - v_age1.                              " 15 days " Cnanges made by Jaiprakash
   v_date2 = p_dateon - v_age2.                              " 30 days " Cnanges made by Jaiprakash
   v_date3 = p_dateon - v_age3.                              " 45 days " Cnanges made by Jaiprakash
   v_date4 = p_dateon - v_age4.                              " 90 days " Cnanges made by Jaiprakash
   v_date5 = p_dateon - v_age5.                              " 180 days " Cnanges made by Jaiprakash
   v_date6 = p_dateon - v_age6.                              " 360 days " Cnanges made by Jaiprakash
   v_date7 = p_dateon - v_age7.                              " 360 days " Changes made by Jaiprakash
   IF NOT it_bseg IS INITIAL.
*    DELETE it_bseg FROM wa_bseg WHERE segment = ''.
     DATA: lv_add TYPE i.
     DATA: lv_date TYPE sy-datum.
     LOOP AT it_bsid INTO wa_bsid.
       wa_final-zterm = wa_bsid-zterm.
       wa_final-zbd1t = wa_bsid-zbd1t.
       CLEAR wa_bseg.
       READ TABLE it_bseg INTO wa_bseg WITH KEY belnr = wa_bsid-belnr.
       IF sy-subrc EQ 0.
         wa_final-segment = wa_bseg-segment.
         wa_final-prctr   = wa_bseg-prctr.
         IF wa_bsid-shkzg = 'H'.
           wa_bsid-dmbtr = -1 * wa_bsid-dmbtr.
         ENDIF.
         CLEAR wa_faglseg.
         READ TABLE it_faglseg INTO wa_faglseg WITH KEY segment = wa_final-segment.
         IF sy-subrc EQ 0.
           wa_final-name = wa_faglseg-name.
         ENDIF.
         CLEAR wa_cepct.
         READ TABLE it_cepct INTO wa_cepct WITH KEY prctr = wa_final-prctr.
         IF sy-subrc EQ 0.
           wa_final-ltext = wa_cepct-ltext.
         ENDIF.
* Calculation for the age buckets of <15, <30, <45, <90, <180 , <360 and >360 days
*        IF     wa_bsid-zfbdt <= p_dateon AND wa_bsid-zfbdt > v_date1.
*          l_age1 = wa_bsid-dmbtr + l_age1.
*        ELSEIF wa_bsid-zfbdt <= v_date1 AND wa_bsid-zfbdt > v_date2.
*          l_age2 = wa_bsid-dmbtr + l_age2.
*        ELSEIF wa_bsid-zfbdt <= v_date2 AND wa_bsid-zfbdt > v_date3.
*          l_age3 = wa_bsid-dmbtr + l_age3.
*        ELSEIF wa_bsid-zfbdt <= v_date3 AND wa_bsid-zfbdt > v_date4.
*          l_age4 = wa_bsid-dmbtr + l_age4.
*        ELSEIF wa_bsid-zfbdt <= v_date4 AND wa_bsid-zfbdt > v_date5.
*          l_age5 = wa_bsid-dmbtr + l_age5.
*        ELSEIF wa_bsid-zfbdt <= v_date5 AND wa_bsid-zfbdt > v_date6.
*          l_age6 = wa_bsid-dmbtr + l_age6.
*        ELSEIF wa_bsid-zfbdt <= v_date7.
*          l_age7 = wa_bsid-dmbtr + l_age7.
*        ENDIF.
         IF     wa_bsid-zfbdt <= p_dateon AND wa_bsid-zfbdt > v_date1.
           l_age1 = wa_bsid-dmbtr + l_age1.
         ELSEIF wa_bsid-zfbdt <= v_date1 AND wa_bsid-zfbdt > v_date2.
           l_age2 = wa_bsid-dmbtr + l_age2.
         ELSEIF wa_bsid-zfbdt <= v_date2 AND wa_bsid-zfbdt > v_date3.
           l_age3 = wa_bsid-dmbtr + l_age3.
         ELSEIF wa_bsid-zfbdt <= v_date3 AND wa_bsid-zfbdt > v_date4.
           l_age4 = wa_bsid-dmbtr + l_age4.
         ELSEIF wa_bsid-zfbdt <= v_date4 AND wa_bsid-zfbdt > v_date5.
           l_age5 = wa_bsid-dmbtr + l_age5.
         ELSEIF wa_bsid-zfbdt <= v_date5 AND wa_bsid-zfbdt > v_date6.
           l_age6 = wa_bsid-dmbtr + l_age6.
         ELSEIF wa_bsid-zfbdt <= v_date7.
           l_age7 = wa_bsid-dmbtr + l_age7.
         ENDIF.
         wa_final-kunnr = wa_bsid-kunnr.
         CLEAR wa_kna1.
         READ TABLE it_kna1 INTO wa_kna1 WITH KEY kunnr = wa_bsid-kunnr.
         IF sy-subrc EQ 0.
           wa_final-name1 = wa_kna1-name1.
           wa_final-ort01 = wa_kna1-ort01.
         ENDIF.
         lv_add = wa_final-zbd1t.
*     lv_add = wa_final-zbd1t.
         CLEAR:lv_date.
         CALL FUNCTION 'FKK_ADD_WORKINGDAY'
           EXPORTING
             i_date      = wa_final-budat
             i_days      = lv_add
*           I_CALENDAR1 =
*           I_CALENDAR2 =
           IMPORTING
             e_date      = lv_date
*           E_RETURN    =
         wa_final-age1 = l_age1.
         wa_final-age2 = l_age2.
         wa_final-age3 = l_age3.
         wa_final-age4 = l_age4.
         wa_final-age5 = l_age5.
         wa_final-age6 = l_age6.
         wa_final-age7 = l_age7.
         wa_final-total = wa_final-age1 + wa_final-age2 + wa_final-age3 + wa_final-age4 + wa_final-age5 + wa_final-age6 + wa_final-age7.
*          wa_final-age1 = l_age1.
*          wa_final-age2 = l_age2.
*          wa_final-age3 = l_age3.
*          wa_final-age4 = l_age4.
*          wa_final-age5 = l_age5.
*          wa_final-age6 = l_age6.
*          wa_final-age7 = l_age7.
*         wa_final-total1 = wa_final-age1 + wa_final-age2 + wa_final-age3 + wa_final-age4 + wa_final-age5 + wa_final-age6 + wa_final-age7.
*        wa_final-age1 = l_age1.
*         wa_final-age2 = l_age2.
*         wa_final-age3 = l_age3.
*         wa_final-age4 = l_age4.
*         wa_final-age5 = l_age5.
*         wa_final-age6 = l_age6.
*         wa_final-age7 = l_age7.
*         wa_final-total1 = wa_final-age1 + wa_final-age2 + wa_final-age3 + wa_final-age4 + wa_final-age5 + wa_final-age6 + wa_final-age7.
         IF p_dateon GT lv_date.
           wa_final-age1 = l_age1.
           wa_final-age2 = l_age2.
           wa_final-age3 = l_age3.
           wa_final-age4 = l_age4.
           wa_final-age5 = l_age5.
           wa_final-age6 = l_age6.
           wa_final-age7 = l_age7.
           wa_final-total1 = wa_final-age1 + wa_final-age2 + wa_final-age3 + wa_final-age4 + wa_final-age5 + wa_final-age6 + wa_final-age7.
         ELSE.
           wa_final-age1 = l_age1.
           wa_final-age2 = l_age2.
           wa_final-age3 = l_age3.
           wa_final-age4 = l_age4.
           wa_final-age5 = l_age5.
           wa_final-age6 = l_age6.
           wa_final-age7 = l_age7.
           wa_final-total2 = wa_final-age1 + wa_final-age2 + wa_final-age3 + wa_final-age4 + wa_final-age5 + wa_final-age6 + wa_final-age7.
         ENDIF.
         APPEND wa_final TO it_final.
         CLEAR: wa_final,l_age1,l_age2,l_age3,l_age4,l_age5,l_age6,l_age7.
       ENDIF.
     ENDLOOP.
   ENDIF.
   IF it_final IS NOT INITIAL.
     SORT it_final BY kunnr segment.
     LOOP AT it_final INTO wa_final.
       MOVE wa_final TO wa_final1.
       wa_final1-prctr = ''.
       wa_final1-ltext = ''.
       wa_final1-segment = ''.
       wa_final1-name = ''.
       wa_final1-zterm = ''.
       AT END OF name1.
         SUM.
         wa_final1-total = wa_final-total.
         wa_final1-total1 = wa_final-total1.
         wa_final1-total2 = wa_final-total2.
         wa_final1-age1 = wa_final-age1.
         wa_final1-age2 = wa_final-age2.
         wa_final1-age3 = wa_final-age3.
         wa_final1-age4 = wa_final-age4.
         wa_final1-age5 = wa_final-age5.
         wa_final1-age6 = wa_final-age6.
         wa_final1-age7 = wa_final-age7.
         COLLECT wa_final1 INTO it_final1.
         CLEAR wa_final1.
       ENDAT.
     ENDLOOP.
   ENDIF.
ENDFORM. " PROCESS_DATA
**&      Form ALV_DISPLAY
**       text
** --> p1        text
** <-- p2        text
FORM alv_display .
   DATA : v_col TYPE i VALUE 1.
   CLEAR wa_fieldcat.
   v_col = v_col + 1.
   wa_fieldcat-col_pos   = v_col.
   wa_fieldcat-seltext_m = 'Customer Code'.
   wa_fieldcat-fieldname = 'KUNNR'.
   wa_fieldcat-tabname   = text-002.
   wa_fieldcat-key       = 'X'.
   wa_fieldcat-outputlen = 14.
   APPEND wa_fieldcat TO it_fieldcat.
   CLEAR wa_fieldcat.
   wa_fieldcat-col_pos   = v_col.
   wa_fieldcat-seltext_m = 'Customer Name'.
   wa_fieldcat-fieldname = 'NAME1'.
   wa_fieldcat-tabname   = text-002.
   wa_fieldcat-key       = 'X'.
   wa_fieldcat-outputlen = 14.
   APPEND wa_fieldcat TO it_fieldcat.
   CLEAR wa_fieldcat.
   v_col = v_col + 1.
   wa_fieldcat-col_pos   = v_col.
   wa_fieldcat-seltext_m = 'City'.
   wa_fieldcat-fieldname = 'ORT01'.
   wa_fieldcat-tabname   = text-002.
   wa_fieldcat-key       = 'X'.
   wa_fieldcat-outputlen = 35.
   APPEND wa_fieldcat TO it_fieldcat.
***   CLEAR wa_fieldcat.
***   v_col = v_col + 1.
***   wa_fieldcat-col_pos   = v_col.
***   wa_fieldcat-seltext_m = 'Payment Term'.
***   wa_fieldcat-fieldname = 'ZTERM'.
***   wa_fieldcat-tabname   = text-002.
***   wa_fieldcat-key       = 'X'.
***   wa_fieldcat-outputlen = 14.
***   APPEND wa_fieldcat TO it_fieldcat.
* CLEAR wa_fieldcat.
* v_col = v_col + 1.
* wa_fieldcat-col_pos   = v_col.
* wa_fieldcat-seltext_m = 'No. Of Days'.
* wa_fieldcat-fieldname = 'ZBD1T'.
* wa_fieldcat-tabname   = text-002.
* wa_fieldcat-key       = 'X'.
* wa_fieldcat-outputlen = 14.
* APPEND wa_fieldcat TO it_fieldcat.
* CLEAR wa_fieldcat.
* v_col = v_col + 1.
* wa_fieldcat-col_pos   = v_col.
* wa_fieldcat-seltext_m = 'Baseline Date'.
* wa_fieldcat-fieldname = 'ZFBDT'.
* wa_fieldcat-tabname   = text-002.
* wa_fieldcat-key       = '

Re-transport the transport request in Quality server after System refresh

Similar Messages

Maybe you are looking for