on 05-23-2008 5:02 AM
can any post OSS# 313991... plzzz
full rewards..
Thanks
MMN
Summary
Symptom
You cannot start mass imports (Import ALL) because not all affected requests have yet been approved by the Quality Assurance procedure of the Transport Management System (TMS).
When you attempt to start a mass import in TMS, the dialog box terminates with message XT659:
Not all requests have been approved.
Scheduled imports terminate with the following error message:
Transport control program tp ended with error code 0250, error text: inactive entries found in buffer.
Other terms
Import approved requests, tp error code 0250, TMS QA
Reason and Prerequisites
Prerequisites:
You activated the TMS Quality Assurance procedure. Information on this topic can be found in the online help for TMS (transaction code STMS) under: Approval or refusal of requests
You work with the individual shipment strategy; however, the requests should be imported automatically (after the QA approval) to the production system at specific times. A periodic mass import is scheduled to do this in the TMS.
Cause:
In the TMS, it is not intended that all approved requests of an import queue can be imported by mass import.
Solution
If all approved requests should be periodically imported into the production system, you must place a virtual system (VDE) between the quality assurance system (QAS) and the production system (PRD).
You can use the RSTMS_DIST_APPROVED_REQUESTS program to transfer all approved requests from the VDE system to the PRD system. You can periodically schedule this program in the QAS system.
1. Configuring virtual system
You must create the VDE system in TMS as a virtual system with the QAS communication system (see TMS documentation: Configuring Virtual SAP Systems). You can choose any system names for the QAS and VDE systems.
2. Changing transport route configuration
In the TMS, you must make the following change in the transport route configuration:
Before: DEV -k-> QAS -b-> PRD
After: DEV -k-> QAS -b-> VDE -b-> PRD
Key: -k-> consolidation method; -b-> supply method
Variants:
If you activated the extended transport control (client-specific transport routes), you can also configure several supply paths between QAS and VDE as well as between VDE and PRD.
Example:
DEV -k-> QAS -003003-> VDE -003300-> PRD
QAS -010010-> VDE -010100-> PRD
(-nnn--iii-> supply method from client nnn to iii)
If you want to supply several production systems, you can also configure several supply paths from the VDE system.
Example:
DEV -k-> QAS -b-> VDE -b-> PR1
VDE -b-> PR2
Process
Due to the import of requests in the QAS system, these are inactively (status: Request must still be approved) transferred to the VDE system.
Due to the approval of a request in the QAS system, this becomes active in the import queue of system VDE (status: Request is ready for import). Refused requests receive the following status: Request was refused.
The RSTMS_DIST_APPROVED_REQUESTS program is used to transfer the requests with the status "Request is ready for import" from the VDE import queue to the supply system of VDE (that is, the PRD production system or, if necessary, several production systems and clients) and then to delete them from the import queue of VDE. Refused requests (status: Request was refused) are also deleted from the VDE queue.
You can choose between the following options:
o Transfer all approved requests:
All approved requests from the VDE queue which are before the end mark (stop mark) are transferred. All requests that have not yet been processed with the QA procedure remain in the VDE queue until a decision (approval or refusal) has been made.
Caution
The processing time point in the QA system determines when a request is transferred to the production system. This can mean that requests are not imported in the export sequence into the production system. The risks associated with this are described in the TMS documentation at:
Execution of transports -> Import for individual requests
o Up to the 1st inactive request:
All approved requests that are before the 1st inactive request (that is, for which the QA decision has not yet been carried out) are transferred from the VDE queue. Approved requests after the 1st inactive request are therefore not transferred. As a result, the requests are imported into the production system in the export sequence.
Note
The RSTMS_DIST_APPROVED_REQUESTS program can only be executed in the QAS system; in all other systems, the program terminates with an error message. In addition, RSTMS_DIST_APPROVED_REQUESTS checks the TMS configuration; the supply is executed only if a corresponding virtual system and the appropriate transfer directions are configured (as described above).
o For executing the RSTMS_DIST_APPROVED_REQUEST program, you require the authorization for the QTEA value of the S_CTS_ADMI authorization object (field CTS_ADMFCT). This authorization is contained in authorization S_CTS_ADMIN by default.
The import to the production systems can be periodically scheduled in the TMS as a mass import. Only those requests for which the QA approval was given and which were already transferred from the VDE queue into the import queues of the production systems are imported. The RSTMS_DIST_APPROVED_REQUESTS program should therefore be scheduled with the same period as the import process, but its start time should be approximately 5 minutes before the import process.
Restrictions
No advance transports should be carried out in the QAS system. Due to an advance transport, the transfer is carried out automatically into the supply systems into which the request can also be imported in advance. In the regular import of the request into the QAS system, the transfer is carried out again; the sequence in the queue of the supply systems is thereby corrected. This correction of the sequence can not be transferred from the program to the production systems by RSTMS_DIST_APPROVED_REQUESTS.
Using the CTS project status switch in the Transport Organizer: When you select "All configured transport targets", the systems behind the QAS system are not displayed. You can set the status switches by directly specifying the systems concerned.
Displaying predecessor relationships in the TMS import queue: Predecessor relationships are not displayed in the import queue of the VDE virtual system. Dependencies between requests from different projects can only be displayed in the Workbench Organizer (Goto -> Dependency comments).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Summary
Symptom
You cannot start mass imports (Import ALL) because not all affected requests have yet been approved by the Quality Assurance procedure of the Transport Management System (TMS).
When you attempt to start a mass import in TMS, the dialog box terminates with message XT659:
Not all requests have been approved.
Scheduled imports terminate with the following error message:
Transport control program tp ended with error code 0250, error text: inactive entries found in buffer.
Other terms
Import approved requests, tp error code 0250, TMS QA
Reason and Prerequisites
Prerequisites:
You activated the TMS Quality Assurance procedure. Information on this topic can be found in the online help for TMS (transaction code STMS) under: Approval or refusal of requests
You work with the individual shipment strategy; however, the requests should be imported automatically (after the QA approval) to the production system at specific times. A periodic mass import is scheduled to do this in the TMS.
Cause:
In the TMS, it is not intended that all approved requests of an import queue can be imported by mass import.
Solution
If all approved requests should be periodically imported into the production system, you must place a virtual system (VDE) between the quality assurance system (QAS) and the production system (PRD).
You can use the RSTMS_DIST_APPROVED_REQUESTS program to transfer all approved requests from the VDE system to the PRD system. You can periodically schedule this program in the QAS system.
1. Configuring virtual system
You must create the VDE system in TMS as a virtual system with the QAS communication system (see TMS documentation: Configuring Virtual SAP Systems). You can choose any system names for the QAS and VDE systems.
2. Changing transport route configuration
In the TMS, you must make the following change in the transport route configuration:
Before: DEV -k-> QAS -b-> PRD
After: DEV -k-> QAS -b-> VDE -b-> PRD
Key: -k-> consolidation method; -b-> supply method
Variants:
If you activated the extended transport control (client-specific transport routes), you can also configure several supply paths between QAS and VDE as well as between VDE and PRD.
Example:
DEV -k-> QAS -003003-> VDE -003300-> PRD
QAS -010010-> VDE -010100-> PRD
(-nnn--iii-> supply method from client nnn to iii)
If you want to supply several production systems, you can also configure several supply paths from the VDE system.
Example:
DEV -k-> QAS -b-> VDE -b-> PR1
VDE -b-> PR2
Process
Due to the import of requests in the QAS system, these are inactively (status: Request must still be approved) transferred to the VDE system.
Due to the approval of a request in the QAS system, this becomes active in the import queue of system VDE (status: Request is ready for import). Refused requests receive the following status: Request was refused.
The RSTMS_DIST_APPROVED_REQUESTS program is used to transfer the requests with the status "Request is ready for import" from the VDE import queue to the supply system of VDE (that is, the PRD production system or, if necessary, several production systems and clients) and then to delete them from the import queue of VDE. Refused requests (status: Request was refused) are also deleted from the VDE queue.
You can choose between the following options:
Transfer all approved requests:
All approved requests from the VDE queue which are before the end mark (stop mark) are transferred. All requests that have not yet been processed with the QA procedure remain in the VDE queue until a decision (approval or refusal) has been made.
Caution
The processing time point in the QA system determines when a request is transferred to the production system. This can mean that requests are not imported in the export sequence into the production system. The risks associated with this are described in the TMS documentation at:
Execution of transports -> Import for individual requests
Up to the 1st inactive request:
All approved requests that are before the 1st inactive request (that is, for which the QA decision has not yet been carried out) are transferred from the VDE queue. Approved requests after the 1st inactive request are therefore not transferred. As a result, the requests are imported into the production system in the export sequence.
Note
The RSTMS_DIST_APPROVED_REQUESTS program can only be executed in the QAS system; in all other systems, the program terminates with an error message. In addition, RSTMS_DIST_APPROVED_REQUESTS checks the TMS configuration; the supply is executed only if a corresponding virtual system and the appropriate transfer directions are configured (as described above).
For executing the RSTMS_DIST_APPROVED_REQUEST program, you require the authorization for the QTEA value of the S_CTS_ADMI authorization object (field CTS_ADMFCT). This authorization is contained in authorization S_CTS_ADMIN by default.
The import to the production systems can be periodically scheduled in the TMS as a mass import. Only those requests for which the QA approval was given and which were already transferred from the VDE queue into the import queues of the production systems are imported. The RSTMS_DIST_APPROVED_REQUESTS program should therefore be scheduled with the same period as the import process, but its start time should be approximately 5 minutes before the import process.
Restrictions
No advance transports should be carried out in the QAS system. Due to an advance transport, the transfer is carried out automatically into the supply systems into which the request can also be imported in advance. In the regular import of the request into the QAS system, the transfer is carried out again; the sequence in the queue of the supply systems is thereby corrected. This correction of the sequence can not be transferred from the program to the production systems by RSTMS_DIST_APPROVED_REQUESTS.
Using the CTS project status switch in the Transport Organizer: When you select "All configured transport targets", the systems behind the QAS system are not displayed. You can set the status switches by directly specifying the systems concerned.
Displaying predecessor relationships in the TMS import queue: Predecessor relationships are not displayed in the import queue of the VDE virtual system. Dependencies between requests from different projects can only be displayed in the Workbench Organizer (Goto -> Dependency comments).
Header Data
Release Status: Released for Customer
Released on: 26.09.2005 06:46:50
Priority: Correction with medium priority
Processor: Gesine Stanienda
Responsible: Hans-Juergen Hennrich
Category: Workaround for missing functionality
Primary Component: BC-CTS-TMS Transport Management System
Affected Releases
Software
Component Release From
Release To
Release And
subsequent
SAP_APPL 46 46B 46B
SAP_APPL 46C 46C 46C
SAP_BASIS 46 46B 46D
SAP_BASIS 60 610 620
Correction delivered in Support Package
Support
Packages Release Package
Name
SAP_BASIS 46B SAPKB46B17
SAP_BASIS 46B SAPKB46B25
SAP_BASIS 46C SAPKB46C08
SAP_BASIS 46C SAPKB46C15
SAP_BASIS 46D SAPKB46D03
SAP_BASIS 46D SAPKB46D06
Related Notes
1090217 - RSTMS_DIST_APPROVED_REQUESTS terminates with tp error 203
Print Selected Notes (PDF)
Action Log
Date Time Initiator Action
29.06.2000 18:47:44 Hans-Juergen Hennrich (D003140) Note Entered
Person Responsible Hans-Juergen Hennrich
Set Status In Process
05.07.2000 12:19:43 Hans-Juergen Hennrich (D003140) Note Changed
06.07.2000 09:21:21 Angelika Kamm-Schaper (D019212) Note Changed
06.07.2000 13:23:05 Hans-Juergen Hennrich (D003140) Note Changed
Status Changed In Process Released for Customer
20.07.2000 10:12:22 METAL Note Translated DE EN
14.08.2000 09:39:29 Peter Krueger (D022803) Note Changed
Status Changed Released for Customer For Checking
14.08.2000 13:04:02 Peter Krueger (D022803) Note Changed
Status Changed For Checking In Process
08.09.2000 14:49:45 Hans-Juergen Hennrich (D003140) Note Changed
Status Changed In Process Released for Customer
08.09.2000 14:50:44 Dorothea Meister (D021416) Note Changed
Correction/Task Recorded SAPKB46B17
08.09.2000 14:51:41 Dorothea Meister (D021416) Note Changed
Correction/Task Recorded SAPKB46C08
08.09.2000 14:52:20 Dorothea Meister (D021416) Note Changed
Correction/Task Recorded SAPKB46D03
18.09.2000 07:22:02 Akiyo Kinoshita (I019122) Note Translated EN JA
24.01.2001 16:20:08 Hans-Juergen Hennrich (D003140) Note Changed
24.01.2001 16:35:59 Dorothea Meister (D021416) Note Changed
Correction/Task Recorded SAPKB46B25
24.01.2001 19:23:44 Hans-Juergen Hennrich (D003140) Note Changed
25.01.2001 08:03:13 Dorothea Meister (D021416) Note Changed
Correction/Task Recorded SAPKB46C15
25.01.2001 08:03:52 Dorothea Meister (D021416) Note Changed
Correction/Task Recorded SAPKB46D06
07.03.2001 17:02:15 METAL Note Translated DE EN
28.06.2001 16:29:08 Hans-Juergen Hennrich (D003140) Note Changed
06.08.2001 18:23:04 METAL Note Translated DE EN
23.06.2003 11:12:25 METAL Note Translated EN JA
26.09.2005 08:46:28 Gesine Stanienda (I030984) Note Changed
Text Changed
Version Generated
Status Changed Released for Customer In Process
26.09.2005 08:46:51 Gesine Stanienda (I030984) Note Changed
Status Changed In Process Released for Customer
26.09.2005 17:50:56 METAL Note Translated DE EN
17.04.2008 01:09:02 CSS_SUPPORT Note Changed
Reeward if helpful.
Thanks and Regards,
Naveen Dsari.
Source: SAP Service Market Place
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
8 | |
7 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.