Technical status nd QM status

hi..
wat is the expansion of QM??...nd wat is technical status nd QM status..
regards
indu

QM is overall status of the request.
Technical status might be correct sometimes but the QM may be errorneous.
Secondly you cannot change the Technical Status but you can QM status.
Thanks,
Manu
Assign points if found Useful
Message was edited by:
Manu Gupta

Similar Messages

Overall status yellow, but technical status is green

We are on SAP BI 7.0, SP 17.
I am having an issue with a few DTP's. I am loading from a cube to 3 DSO's. The process was working correclty for quite a while, but lately has been running extremely long. For something like 7,000 to 8,000 records it takes only 43 seconds for the DTP to finish and the technical status to change to green. However, it takes 2 hours for the overall status to change to green and sometimes it doesn't at all and I have to set it to red so that I can delete it.
While it is trying to change the overall status to green the DSO is locked - I can't get into the DSO manage screen - gives me an error message about the locks. I have read some fairly similar posts already, but none that I have seen seem to have the exact issue as I'm having. Does anyone have any ideas why the overall status is not being updated?
I have tried re-activating the target DSO, source cube and DTP, but that didn't work. I also tried to create a brand new DTP, but that also didn't work. Also, this process is already in a process chain. I am compressing the cube on a weekly basis. Any help is greatly appreciated.
Thanks
Brett

Hi Brett.
We are experiencing similar problems. I am loading initial load from a DSO with a very high number of requests to a infocube.
Apparently there is a overflow of the lock table (SM12). There is a lock for each request in the DSO and when the number of locks reaches 3500 the DTP stalls. If I manually set the overall status to green, I get the lock table overflow error message.
I've told my basis team to increase the enque/table_size parameter, I'll let you if that has any effect.
Regards,
Lars

Forcing technical status to RED

I have a load running for a while. I turned the overall status to red, but the technical status remains yellow and its still picking up records from source system. I tried killing the process in SM50, the jobs seems to die but to only reappear after sometime. I think I need to turn my technical status to red, to stop the process.
How can i turn the technical status to red? Any inputs or pointers would be appreciated.

tell your basis team to stop the job in SM50, as these jobs requires special authorization for cancelation which only admin person can do:)
@KJ...

Technical Status is in yellow but total status is in Red

Folks,
My Init load failed due to RFC errors, in the monitor Total is showing Red Status but the Technical is still showing yellow status and I am unable to delete the failed PSA request to re-start my Init load, please let me know how to resolve this issue.
Thanks,
Kumar

Hi ,
did you cancel the job in source system .. first cancel that job and the delete that request ..
request might take long to delete due the more no of records ..
check the deletion job in source system wether its progressing or not .. In general you can follow this if you face this kind of issue further ..
regards,
shikha

QM & Technical Status are RED thouh request is running

Hi,
I have one request which is running even now-- (load to ODS)
in the monitor the request is running but in the manage tab of the data target both traffic lights of technical And QM status were RED!
Before the load was scheduled i had changed the ODS settings to see the QM status automatically and activate the ODS data data automatically.
This is very huge dataload and if there is anything wrong then i need to change it immedietly ! it takes nearly 40 hours to finsih this load--
Should there anything to change or is it OK?
Raj

Hi Raj
In General the moment you made the Qm status to RED it is
automatically stop all the related jobs or process in some
pecular cases you to kill the process via SM 50 . Just conatc t
your BASIS people immdeiately on this and ask themn to kill
the process related to the request.
And do the rest of the process like deltion of the request or
what ever...
Hope it helps you ..!
Cheers
K M R
Assigning points is the only way of saying thanx in SDN***
>
Raj Karan wrote:
> Hi,
>
> I have one request which is running even now-- (load to ODS)
>
> in the monitor the request is running but in the manage tab of the data target both traffic lights of technical And QM status were RED!
>
> Before the load was scheduled i had changed the ODS settings to see the QM status automatically and activate the ODS data data automatically.
>
> This is very huge dataload and if there is anything wrong then i need to change it immedietly ! it takes nearly 40 hours to finsih this load--
>
> Should there anything to change or is it OK?
>
> Raj

DTP Technical status red

Hello all,
I have a BI 7.0 system which is being recently upgraded with EHP1.
After this upgrade we are facing two problems with DTP.
1) The techical status of the DTP is getting red and We have to manually set the status green.Whichever setting we use in update and execute tab.
There is absolutly no problem with the records and there are no records in error stack also.
2) We are geting a short dump of ITAP duplicate key.After we change the setting in DTP to no update no reporting in update tab it runs successfully.
What can be the pronlem.
Please help.
Reagrds,
Pratighya.

Hi ,
Is there any semantic key declaration for this DTP.
The semantic key declaration gets deactivated when u change the setting to No update No reporting
Let me know if there is any sematic key declaration and any routine created in the related transformation
Prathsih

Total QM Status & Technical QM Status difference

Hi,
Can any one brief me what is the difference between Total QM Status & Technical QM Status under Status Tab of RMO?
Regards,
Raj

Hi Rajsekhar,
QM status is used to check the request status normally .
if u have to force any request to red in order to delete the req and reload in those situations you will use the QM .
Right click infoproviders --> click manage
you can see it in the RSMO --> Details tab traffic signal also.
Technical status refers to the internal display of the process like transfer of Idocs from source..
Thanks,
Sudhakar.
assign points if this helps...

ABAP code to set Infopackage Monitor to "RED" status?

Hello,
I have an Infopackage that is using ABAP code to determine the selection values dynamically for an Infoobject during the load (Type: 6 ABAP routine). We have built in customer error checking on the selection values based on our requirements.
In the event of an error I need to do the following:
    -Set the 'Total' and 'Technical' color status to "RED" in monitor.
    -Define custom error message in "Status" tab of monitor for load.
Does anyone know how to accomplish this? Links to an example or previous thread will be appreciated.
Thank you,
Brian
Message was edited by:
        Brian

The status of a particular request is stored in the table RSREQDONE. You can have an abap code to modify the entries of the field TSTATUS (technical status of the request) in this table for the given request number.
Example:
Value of @5B@ for this field denotes that this request is successful (GREEN)
FYI, I am not sure how recommendable this process is coz I never implemented before.

DTP load in Yellow status forever

All,
The DTP load to this particular remains in Yellow status forever even though the transferred records are just 5000. After observing the dump, it shows problem where a select query to a table is done in the end routine of the transfroamtion.
The select is on a big master data table (material) but when I gave the selection by itself in SE16, there were not many records - just 3000. then why would the trace say that all the time is being spent querying this database table?
This was all working in D but not in q
Another important note is that there was no scuh change to the material table. however, there were four attributes to which we had enabled 'conversion' in the transfer structure
Would this be an issue if not the code itself?
Thanks

Any updates please?
MORE iNFORMATION:
The dtp loads from one DSO to another. I checked a similar scenario in the same system - things look fine.
I have an end routine in the transformation. when I look at the dtp monitor for the status, it says:
Extract. from DataStore xxxx: 4709 Data Records ---status GREEN
Filter Out New Records with the Same Key : 5000 -> 5000 Data Records------status GREEN
ODSO xxxxx-> ODSO yyyyy-----status YELLOW
-Transformation Start---status GREEN
-Rules---status GREEN
-End Routine---status GREEN
No Message: Transformation End
No Message: Update to DataStore Object yyyyyy
No Message: Set Technical Status to Green
No Message: Set Overall Status to Green
Thanks!

PS-Relationship between the system status in wbs elements and activities.

Relationship between the system status in wbs elements and activities.
We have the following requeriment with the system status in PS. We have a project with complete technically status and we want to undo the complete technically status in one activity without changing the complete technically status in the WBS element or the project.
The reason is that after putting the complete technically status, users have to change the values in the P.O. We don´t want "open" all the project and we only need to "open" the activity where the P.O. are in.
Is that possible? How is connected the system status between activities, wbs elements and the project son I can change the status in the below step without changing the higher steps?
Thanks in advance.

Hi Bala
Yes, you have put it rather correctly.
We use WBS elements for booking and posting time (client requirement). So what I am looking for is WBS Elements with the system status TERL (Time and Expense Released).
I talked of the deletion flag also, because a WBS element flagged for deletion can't be used. It's one of the criteria to screen the WBS elements.
I hope it's clearer now.
Vinitha.

Data Package 1 ( 0 Data Records ) at DTP with Status RED

Hi All,
For 0 records at DTP level it is showing Overall status & Technical status as RED and yellow beside Data Package 1 ( 0 Data Records ). There is no short dump no error message. At PSA level in status tab the message displayed is Status 8 which says no data on R3 side for this particular load. Help me out.
Regards,
Krishna.

Hi,
if traffic light is not highlighted, you are probably running a delta.
You will have to set the traffic light in the according init.
(and run init again )
the setting in the delta will be the same.
Udo

PSA deletion -clarification regarding QM status

Hi Guru's
We r on BI 7.0 SP13. We are loading HR data with full loads via infopackages to PSA and subsequently from PSA to infocubes via DTP. We have configured a process chain to delete the PSA requests which are 1 day old in order to make sure that we do not have duplicate records uploaded via DTP from PSA to infocube.
The setting on the PSA deletion is to delete requests that are 1 day old and only sucessfully booked requests/updated in data targets. If we maintain this setting system is not deleting the PSA requests which are more than i day old. but if i remove the checkbox for "only successfully booked requests" system deletes all requests which are more than 1 day old.
When i checked the status of the requests, it has a "green" color for technical status and the radio button " back to technical status" is selected. My question is Does the system check if these PSA requests are having QM status is green before deleting them if we select "only sucessfully booked requests"? if yes how to set the QM status as green automatically in the requests that are only loaded to PSA?
i also verified the table RSREQDONE in order to check if these PSA requests are having "QM status fields" populated. only technical status were green for these and the QM status fields were not populated.
I want to get a clarification whether these requests that load to" PSA only" are supposed to have a QM status or they are supposed to have only the technical status? if they are suppose to have a QM status , then how to set it automatically ?
thanks

Hi Anil,
Full Upload Request does not concern any DELTAs whatsoever. Just populate the SETUP Tables in R/3, give parameters (if any) and load, thats it. Thats why you dont need to switch previous request to RED because a FULL Request does not care on the status of the last update.
DELTA Update Request is different. The system needs to know if the last DELTA extraction was a failure or success. It needs this info so that the system will know if it will request for a new fresh batch of updates (DELTAS/Changes) or RESEND previous batch of updates (DELTAS/CHANGES) in case the previous DELTA Update is a failure...
Hope I have helped. If i did, please grant points...
--Jkyle

Transmission status mismatch in datasource 0BBP_TD_SC_1 (SRM Analytics)

Hi,
Following is brief summary of the issue:
General Business Process
Shopping Carts are created and ordered on a daily basis. we are using Extended Classic Scenario the follow on document is typically a local Purchase Order. For reporting purpose the data (SC and also PO) are extracted to BI. An initial extraction has been done and thus data is extracted using delta extraction to BI (every 8 hours)
Issue summary
For Shopping Carts a follow on document for all items is created (thus the technical status I1113 u2013 u2018Follow-on Document Createdu2019 is set for all items). Now the SC is extracted to BI, but there this status (I1113) is only displayed for some item, but not for all items (e.g. status I1113 is not set for item 1, but for item 2 &3 or status I1113 is not set for item 2, but item 1 &3).The issue occurs for all kind of SC, independent on the number of items (has been seen for SC with just 1 item, but also with 18 items and in between). The result is that there is a mismatch between SRM and BI. The document status is set correctly in the SRM database, the issue happens only for the data extraction. It works fine for the initial extraction, the issue above only occurs for delta extraction. Also issue is happening only in production system. Not able to replicate in quality or developement system.
Any suggestion or clue how rectify the mismatch status.

Dear Poster
Your thread has had no response since it's creation over
2 weeks ago, therefore, I recommend that you either:
- Rephrase the question.
- Provide additional Information to prompt a response.
- Close the thread if the answer is already known.
Thank you for your compliance in this regard.
Jason Boggans
SAP SRM SDN Moderator

PLM7.02: Status & Release Management/ Status and Action Management

Hello,
                I´d like to know if anybody worked with Status & Release Management. And has some example to how we can customize: SAM (Status and Action Management) in “Define Status Scheme” transaction.
                How it´s works the relationship with: Status: Attributes, Status: Field values, Scheme Definition, Attributes: Definition.
                I´ll appreciated if you could give me a simple example of this functionality.
                Thanks in advance.
                Best Regards from Brazil.
                Rodrigo Arai

Hi Rodrigo,
in a nutshell:
- you can define status network based on objects (w.g. material)
- Define Attributes: you can define attributes like DELETION_ALLOWED or LOCKED_FOR_CHANGE and you can implement preconditions in custom classes when should it happen
- Define Status Field: you can define some fields which are related to the status. e.g. in recipe management RCP_USAGE
- Status: you can define the different statuses (e.g. in process, completed..) with attributes
- Scheme Definition: you can define the logic between statuses. E.g. you would like to swith from status In Process to Completed and from New to In Process. Then switching from New to Completed is not possible for the user.
- Subobject Type Scheme only applied if you have subobjects
here you can find the customizing documentation, there are some examples as well:
Define Status Scheme
Use
In this Customizing activity, you define statuses and status schemes for object types and corresponding attributes.
For each status, you can define which attributes are allowed to be set for an object with this status assigned.
The status scheme defines the initial status and the possible transitions from one status to another.
Activities
You define status schemes as follows:
1. Select the required object type and enter the following:
a) An identifier
b) An object type class (Note: this class should implement the interface class)
c) A subobject type search help
The search help provides a list of all possible subobject types. This feature enhances the usability while maintaining status schemes at subobject-type level.
d) If the
Status
tab page shall be visible on the PLM Web UI, select the
Status Tab
checkbox
Status and action management is a reusable object. It has been modeled as a dependent object. The prerequisites to enable status and action management for any new objects are:
Add the Status and Action Management tab page on the UI.
Enable the Status Tab checkbox in this Customizing activity.
2. Select the required object type and define the following attributes for it:
a) An object type
b) An attribute identifier
c) An attribute description
d) An attribute type
e) Select a precondition class (Note: This class should implement the '/PLMB/IF_SAM_PRECONDITION' interface)
3. Define the technical status field name.
When you change the object status, the system updates the technical status field names to the new values made in these settings.
4. Select object type and define corresponding statuses.
a) Select the status and define the corresponding object type, an identifier, description, and status icon.
Note:
You cannot define new statuses for materials and material BOMs. For these objects, all values should be transferred from the back-end system.
You can import the status values from the back-end system as follows:
b) Select the object type that represents a material or a MatBOM.
c) Select
Status
in the dialog structure.
d) Choose the
New Entries
pushbutton.
e) Choose the
Import Status
pushbutton.
Note
The system imports the following status values into SAM:
For material: the
X-plant matl status
(cross-plant material status)
For MatBOM: the header status
Although you cannot change the imported value for a material or a MatBOM, you can change its name and description to conform to SAM terminology.
You can differentiate between the following cases for objects whose status values are imported from the back-end system:
The object was not created on the PLM Web UI, but in the back-end system; no SAM status scheme or status was assigned, but a status value was set in the back-end system.
If you assign a SAM status scheme to this object later on that contains the equivalent imported status values, the SAM status value is set accordingly, even if any precondition check results of the SAM status scheme may exist.
The object was created in the back-end system or on the Web UI and a SAM status scheme is assigned to the object on the PLM Web UI.
If the corresponding status value is changed in the back-end system, then existing SAM preconditions for this status transition and allowed status transitions are checked. If the preconditions are not fulfilled, a message is raised and the new status cannot be saved.
5. Specify which attributes are allowed for each object type when the chosen status is set.
a) Select a status and open the
Attributes
screen.
b) Choose an object type.
c) Choose an attribute.
6. Define whether values from other technical fields are affected by setting this status.
a) Select a status and open the
Field Values
screen.
b) Select an object type.
c) Select a technical field name.
7. Specify the status scheme. The status scheme defines the initial status and status transition for the object type. For example, below is a list of standard status schemes defined for iPPE object types.
Assembly Header - PLM_PPEAH
Assembly Item - PLM_PPEAI
Product Item Variant - PLM_PPEPIV
Product Variant - PLM_PPEPV
You can also create schemes for the object type as follows:
a) Specify an identifier and description for the status scheme and set one of the statuses defined above as the initial status.
b) Select the status scheme and open the
Transitions
screen. Enter all possible status transitions by specifying the source (
Status From
) and target status (
Status To
c) Select the
Long Text
checkbox if you want the system to open the long text editor on the
Status
tab in the PLM Web UI. You can use the long text editor to create notes for this transition.
8. Define the scheme at subobject-type level by entering following parameters:
a) Object type
b) Subobject type (You can choose from the list of subobject types you have specified when defining the search help in step 1)
Alternatively, you can define a default status scheme that is automatically displayed on the
Status
tab.
The following statuses are included in the standard delivery:
10 - In Work
20 - For Approval
LINKED_DIR
LINKED_MAT
LOCKED_FOR_CHANGE
REPLACE_PH_ASSEMBLY (only in the PLM_PPEAI assembly item and the PLM_PPEPIV product item variant)
30 - Released For Planning
LOCKED_FOR_CHANGE
40 - Released
RELEASED
SUB_ITEM_STATUS
The following status transitions are possible:
FROM
TO
Long Text checkbox (dialog box for notes)
10
20
20
30
30
40
20
40
20
10
X
30
10
X
40
10
X
More on SAP help:
Status and Action Management on the Web UI - SAP Library
Best regards
Tamas

DTP Set Overall Status to not turning to Green, it's remains yellow

Hello,
I'm extracting data from Attributes and loading into SQL data base using openhub destination.
When request the Job, Request status remain Yellow but Technical status of the request is green, but set overall status to green is in Grey colour.
The job is running hours long... even background BW job status got finished.
DTP status at each extraction level screen shot is attached.
Santhosh

Hi,
Have you done below settings at dtp level?
DTP--> Execute tab
Overall Status of Request---> set overall status automatically.
is it delta load?
Seems like its full load. if its full load and backend job was finished then you can make it dtp status as green.
Due to the heavy loads on your bw server its unable to communicate idocs.
Thanks

Technical status nd QM status

Similar Messages

Maybe you are looking for