Component inspection status for query

dear experts,
is there a way i can indicate in my query that for a certain production order's components, the inspection status of each component, whether it has a UD, whether its inspection date has been exceeded?
what field and table can i see this? QALS?

Dear Anirudh,
For verify documents you can use the digital signature concept in combination with a status change. For every status you can maintain a signature strategy which has to be maintained in customizing before. For more information please see the SAP Online Documentation under http://help.sap.com
SAP R/3 Enterprise Application Components
> Cross-Application Components
> Document Management
> Document Info Record
> Approval Using Digital Signatures
Here you will find all necessary information about how to set up digital signature for document info records.
Best regards,
Christoph
P.S.: Please reward points of this information is usefull

Similar Messages

User status for component item in service order (plant maintenance order)

Dear experts,
I cannot find the customizing for assigning a user status (profile) to a component item of a service order.
IW31 - tab components - mark an entry - click on button "component status"
Can you help me?
Best Regards,
Philipp

OSS message created. Answer from SAP:
11.02.2011 - 15:04:46 CET - Antwort von SAP
Hello Mr. Miller,
user status for components are not possible and not intended. I'm
sorry that I cannot provide better news.
Best regards
Reinhard Gruber
Senior Support Consultant
AGS Primary Support,
Business Suite & Technology
SAP AG
Therefore this message is closed... but not yet answered
Edited by: Philipp Miller on Feb 11, 2011 3:28 PM

Error in getting process status for oracle instance: instance12- component: coreapplication_obisch1

Hi,
while uploading new rpd getting error message in enterpriise manger
Error in getting process status for oracle instance: instance12- component: coreapplication_obisch1,chekced in the dignostic log found above mentioned error
what can be cause of the probelm
thanks

Hi,
1.Try using the sample rpd of it works, then the problem with the new rpd.
2. Restart the service once then upload the new rpd.
Regards,
VG

What is the table for query name

Hi All,
I need an urgent requirement for removing duplicate technical query names from the production. Since there are few issues with the SAP given program I am customizing the SAP Program. Can any one tell me what is the table where the QUERY NAME and it's technical name can be found?
Thanks,
Alex.

hi Alex,
try RSRREPDIR, RSZCOMPDIR.
there is one oss note all the tables.
Table containing Work Book and query relation
Query Detailes
oss 792779
Symptom
Report ANALYZE_RSZ_TABLES is designed as a check-tool for detecting and solving different types of inconsistencies in the main query definition database tables.
The program is recommended for BW system administrators.
Other terms
Query definition, query, reusable, component, variable, missing elements, missing records, missing UID, INCONSISTENCY, RSZELTDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZCALC, RSZSELECT, RSRREPDIR.
Reason and Prerequisites
ATTENTION: the described version of the program is delivered with the following Support Packages:
SP27 for release BW 3.0B
SP21 for release BW 3.1C
SP13 for release BW 3.5
All versions of this report available in systems before those Support Packages are test versions which can be used only for information purposes.
Check prerequisites
Checks are possible only for elements in object version 'A' (active) and 'D' (delivered).
Checks for query elements in 'D' version are possible only in the systems which are set as content.
Checks description
Report performs checks in the tables containing the parts of the definitions of queries and query components: RSRREPDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZELTDIR and RSZELTXREF.
1. Table RSRREPDIR
The table RSRREPDIR is a header table of the generated reports. Consistency of query definition in this table allows to select a query in the Open Dialogs of fronted application and to call report generated for this particular query using transaction RSRT.
The following errors can be found:
- queries with missing definition;
- queries with missing GENUNIID;
- queries with technical names different than in RSZCOMPDIR;
- non-queries in the table.
1.1 Queries with missing definition
The queries are available only in the table RSRREPDIR and not found in the table RSZELTDIR in the corresponding object version. Such queries (in active version) can be accessed only from RSRT transaction. An attempt to execute such query will return the short dump 'Exception condition INCONSISTENCY'. The error also happens during query generation in RSRT or during mass regeneration of the queries using RSR_GEN_DIRECT_ALL_QUERIES report or application menu of transaction RSRT. The inconsistent queries can not be repaired because of missing query definitions. The recommended solution is to delete those records in order to avoid the possible system dumps.
1.2 Queries with missing GENUNIID
Queries having empty GENUNIID field in the table RSRREPDIR. Such queries may be available in the frontend and in RSRT transaction. An attempt to execute such query will return the message'GENUNIID not found'. Situation requires additional investigation at SAP. Create an OSS message for BW-BEX-ET-QDEF.
1.3 Queries with technical names different than in RSZCOMPDIR
The check outputs the queries which have different technical names in the RSRREPDIR and RSZCOMPDIR tables. Execution of a query using the technical name given in Query Designer and stored in the table RSZCOMPDIR will return the error message 'GENUNIID not found'. The system tries to find the corresponding GENUNIID for the wrong COMPID which does not exist in the system or which belong to another query. The recommended solution is to correct the wrong COMPID in the table RSRREPDIR via corresponding procedure.
1.4 Non-queries in the table
The table RSRREPDIR normally contains only reports. Query elements of other types should not exist in this table and can be deleted. In case, when such records exist in the table an attempt to access them in RSRT returns the error message 'GENUNIID not found'. The recommended solution is to delete those records from the table using the corresponding procedure.
2. Table RSZCOMPIC
The table RSZCOMPIC contains an InfoProvider assignment for queries and other reusable query components (STR, RKF and CKF).
The following errors can be found:
- local elements in RSZCOMPIC;
- components with inconsistent definition;
- components based on non-existing InfoProviders;
- components based on non-active InfoProviders.
2.1 Local elements in RZSCOMPIC
The table RSZCOMPIC contains an InfoProvider assignment for the reusable components. The local elements and also variables have no InfoProvider assignment and should not exist in this table. Those elements can be deleted via corresponding procedure.
2.2 Components with inconsistent definition
The reusable queries or query components existing in the table RSZCOMPIC, but not found in the table RSZELTDIR. Those reusable components may return 'Exception condition INCONSISTENCY' dump during accessing/execution. The situation may have different outcomes and has to be investigated at SAP. Create an OSS message for BW-BEX-ET-QDEF.
2.3 Components based on non-existing InfoProviders
Queries or query components are assigned to the InfoProviders which do not exist anymore in the system. Queries without InfoProvider are not available in Open Dialogs of frontend applications, but can be executed in RSRT. The execution will return the error message'InfoProvider not found'. The recommended solution is to delete the unnecessary components. Deletion of these queries or query components can be done directly from the list using corresponding procedure similar to RSZDELETE transaction.
2.4 Components based on non-active InfoProviders
Queries or query components which are assigned to the InfoProviders which do not exist in the system in the active version. Queries without active InfoProvider are not available in Open Dialogs of frontend applications. In case, an affected query is technically consistent, an attempt to execute it in transaction RSRT will return the message 'Activate the XXX InfoCube / InfoProvider again. Message #BRAIN 056'. Quite often this error is combined with other errors like missing GENUNIID in the RSRREPDIR or other inconsistencies. Each case has to be investigated in order to get the current status of this object. If the affected query is useless, it can be deleted from the system using transaction RSZDELETE.
The check is available only for the query elements in object version 'A' (active).
3. Table RSZCOMPDIR
The table RSZCOMPDIR is the directory table containing the main properties of all reusable components.
The following errors can be found:
- duplicated technical names (COMPID);
- components with inconsistent definition;
- components without InfoProvider assignment;
- components with missing OWNER.
3.1 Duplicated technical names (COMPID)
The check outputs queries or other reusable query components which have duplicated technical names (COMPID).
The error does not cause any dumps in ABAP or terminations in Query Designer, but may cause several symptoms in different reporting areas:
different queries are available in BEX Analyzer and RSRT under the same name;
wrong query is used as Data Source for Web Template (Web Reporting, Reporting Agent, Broadcasting, MDX);
replacement of variables does not work... etc.
The recommended solution is to provide a new technical name for the duplicated component using corresponding procedure.
ATTENTION: in case when there are only 2 components with the duplicated technical name, only one of those 2 components can be renamed using the corresponding procedure.
The alternative solution for renaming the duplicated technical names is to use the ABAP report RENAME_DUPLICATE_ELEMENTS.
3.2 Components with inconsistent definition
Reusable query components which are not found in the element directory table RSZELTDIR are displayed. This situation may cause the short dump 'Exception condition INCONSISTENCY' during accessing the affected component in Query Designer or execution the affected query in RSRT. Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
3.3 Components without InfoProvider assignment
All reusable query component (except variables) should be assigned to a particular InfoProvider. This assignment is located in the table RSZCOMPIC. When the record is not found in this table, the affected component may become not available in Query Designer in the corresponding InfoProvider. In some cases the error message "Component XXX.. (version A) has no InfoCube assignment". Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
3.4 Components with empty ONWER field
Reusable components which have empty OWNER field in the table RSZCOMPDIR are accessible by users having $USER setting in the authorization object S_RS_COMP1 (users which are authorized to their own queries or query components). This leads to authorization concept violation.
For error solution the field OWNER in the RSZCOMPDIR should be filled with any value. Execute the corresponding edit mode in order to fill the empty field with user 'SAP'. This will prevent the potential authorization violation for users with $USER setting and will take no effect on the users without this setting.
4. Table RSZELTXREF
The table RSZELTXREF contains all links and dependencies between the query elements within a query or query component.
The following errors can be found:
- missing elements (INCONSISTENCY dump);
- not supported relations between query elements;
- extended RSZELTXREF check.
4.1 Missing elements
Missing elements are those query elements which exist as the dependant objects (field TELTUID) in the table RSZELTXREF, but not available in the element directory table RSZELTDIR in corresponding object version. In case, when such elements are used in any query or other query components (STR, CKF or RKF), this may lead to ABAP short dump with 'Exception condition INCONSISTENCY' error message in query run-time or design-time. Other known symptoms of this error is, that structures, calculated key figures or restricted key figures are not available in an Info Provider in Query Designer during design-time.
The missing elements which are in use in other queries or query components, can not be automatically repaired or deleted without components where those elements are used. In most cases the manual repair operations directly in the DB tables are required. Create an OSS message for SAP component BW-BEX-ET-QDEF for further investigations and creation of a repair plan.
The missing elements which are not in use in any query or query components, can be deleted from the system via corresponding delete procedure. This deletion will not affect any existing query or query component.
ATTENTION: if missing element is variable, it can be repaired in some cases automatically using the corresponding repair procedure. See table RSZGLOBV check 5.1. 'Variables with inconsistent definition' for details.
4.2 Not supported relations between query elements
Some relations between query elements which are not supported and can cause dumps in ABAP or terminations in Query Designer (for example link STR <--> VAR). Such cases have to be additionally investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
4.3 Extended RSZELTXREF check
The extended RSZELTXREF check outputs 2 situations which, in combination with other conditions in the system, may be responsible for slow performance of all operations which involve select from the table RSZELTXREF and resolving the relations between query elements (query load, query generation, expanding of a variable list for corresponding InfoObject, expanding of a list of reusable components in Query Designer,... etc.):
- records with empty INFOCUBE field
- records which are not used in any query or query component
Records with empty INFOCUBE field
The current algorithm of resolving of relations between the query elements uses an optimization which allows to reduce the amount of data selected from the table RSZELTXREF during such operations are query load, query generate, expand a list of reusable components (STR, CKF, RKF) and so on. All relations between query elements within one reusable component based on one InfoProvider 'N' are also located within the same InfoProvider. The system has to select only records where the INFOCUBE field contain the same InfoProvider 'N' and in addition to this all other records where the INFOCUBE field is empty. This is necessary, because in all BW releases below 3.x the INFOCUBE field was not in the RSZELTXREF table and all components created before 3.x release have this field empty. Selection of records with empty INFOCUBE is required in order to ensure the consistency of processed query.
When the number of records with empty INFOCUBE is quite large (50.000 - 1 mln records), any simple operation which require resolving of the relations may take a long time, because those records are always being selected, loaded to Query Designer and processed in the design-time.
Records which are not used in any query or query component
The program makes a virtual attempt to reconstruct the table RSZELTXREF via resolving the relations between all reusable components existing in the system. All records which are not used in any query or query components are considered as non-used records. Usually these are fragments of old queries or other components which are not deleted due to former errors in the query delete algorithm.
The current version of the program contain only information about those 2 issues. See the OSS note 823804 for additional information.
ATTENTION: the extended RSZELTXREF check is recommended when all critical problems with reusable components are resolved and the system clean-up is done (no useless records in the tables, no useless non-executable queries or other affected query component available).
Starting from SP28 for BW 30B, SP22 for BW 31C and SP14 for BW 3.5 the Extended RSZELTXREF check detects and fixes the following situations:
records used in existing queries or query components with empty INFOCUBE field;
records used in existing queries or query components with wrong INFOCUBE assignment;
records with or without INFOCUBE assignment which are not used in any query or query component.
For further check details read the OSS note 859086.
5. Table RSZGLOBV
The table RSZGLOBV contains the definitions and technical properties of the variables.
The following errors can be found:
- variables with inconsistent definition;
- variables with missing or incorrect properties;
5.1 Variables with inconsistent definition. Variable not found in RSZELTDIR/RSZCOMPDIR tables.
The variable existing in the table RSZGLOBV, but not existing in the tables RSZELTDIR or RSZCOMPDIR have inconsistent definition. These situation may return 2 different error messages. When a variable is missing in RSZELTDIR table (or in both together), an attempt to expand a list of variable under a corresponding InfoProvider or a list of text/formula variables will return a message 'Inconsistency in loading...'. All variables which are created for corresponding InfoProvider, text/formula variable are not available. When a variable is missing in the RSZCOMPDIR table only the error message is 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded' in Query Designer.
In both cases the variables can be repaired via the corresponding procedure provided in the program under the technical name (COMPID) corresponding to the name in VNAM field in the table RSZGLOBV with the text 'REPAIRED BY SAP'.
As an alternative solution, when the affected variables which are not used in any query or query component can be deleted directly from the RSZGLOBV table. Both solutions will fix the reported symptoms.
ATTENTION: it is recommended to open a repaired variable in Variable Wizard of Query Designer and to adjust the definition of this variable, when it is necessary.
ATTENTION: deletion of the affected variables missing in the table RSZCOMPDIR is not possible using transaction RSZDELETE. An attempt to delete such variable will return the error message 'Component not found'.
5.2 Variables with missing or incorrect properties
Several errors can be found within this check. The variables of different type have their own sets of properties. Missing or incorrect properties may cause different error message during execution of a query where such variables are in use. In the case of the affect variables with processing type 'replacement' , the replacement may not work because of the problem.
Each case has to be investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
6. Table RSZELTDIR
The table RSZELTDIR is the main directory table containing all query elements available in the system.
ATTENTION: the RSZELTDIR check may take a long running time depending upon the table size.
The following errors can be found:
- local elements not in use;
- reusable elements not in RSZCOMPDIR table;
- reusable elements not in RSZCOMPIC table;
- structure (STR) without structure members;
- selections or RKF without definition in RSZSELECT table;
- formulas or CKF without definition in RSZCALC table;
- variables (VAR) without definition in RSZGLOBV table;
- queries (REP) without entries in RSRREPDIR table.
6.1 Local elements not in use
Local elements (field REUSABLE = false) which are not used as dependant objects in the table RSZELTXREF. These elements are useless and not accessible from Query Designer. Usually these are fragments of the definitions of old queries accumulated in system because of different problems with save/delete procedures which are not accessible by the end users. The recommended solution is to delete those elements using the corresponding delete procedure.
6.2 Reusable elements not in RSZCOMPDIR table
Reusable elements (field REUSABLE = true) must have a corresponding entry in the table RSZCOMPDIR which contains the definition and properties of this reusable component. An attempt to load such component in Query Designer may cause the error message 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded'. Additional investigations are requires at SAP. Create an OSS message for BW-BEX-ET-QDEF.
ATTENTION: Deletion of such affected components is also not possible using transaction RSZDELETE. An attempt to delete will return the message 'Component not found'.
6.3 Reusable elements not in RSZCOMPIC table
Reusable elements (field REUSABLE = true), except variables (DEFTP = 'VAR'), must have a corresponding entry in the table RSZCOMPIC which contains an InfoProvider assignment for reusable components. When a reusable component has no InfoProvider assignment it may be not available in Query Designer during design-time. Additional investigations are required at SAP. Create an OSS message for BW-BEX-ET-QDEF. In case the affected component is useless, it can be also deleted from the system using transaction RSZDELETE.
6.4 Structures (STR) without structure members
Reusable and non-reusable structures (DEFTP = 'STR') should have dependant elements (structure members). When these structure members are not found a query containing this structure returns the error message 'Element structure not correct' during generation or execution in RSRT or BEx analyzer. The program outputs a query technical name where such structures are used or the technical name of an InfoProvider if the affected structure is reusable and not used in any query. In this case it can be accessed from any query created in the same InfoProvider in Query Designer. The solution is to open the affected structure in using the latest available version of Query Designer and to create the required structure members in order to avoid the error message.
In case, when the affecter structure is local (non-reusable) and is not used in any query, this structure is not accessible by frontend users and can be deleted from the system by corresponding procedure provided in the program.
6.5 Local selection of RKFs without records in RSZSELECT table
Local selections and reusable Restricted Key Figure (DEFTP = 'SEL') usually should have the corresponding records in the DB table RSZSELECT. The program outputs all selections found in the system which have no corresponding records in the RSZSELECT table.
Usually this issue has no impact on the existing queries and produces no error messages. There are 3 possible types of selections within a query:
Normal selection - this selection represents a characteristic in Row, Columns or Free Characteristics area, Conditions or Exceptions. This situation produces no error messages, but the selection is not taken into account by OLAP.
Dummy structure member - structure member type selection can be defined using Query Designer. Such structure member produces no selection and can be used only as place holder within a query. This situation produces no error messages during generation/execution of a query containing a structure with those dummy structure members.
Cell selection - this type of selection is usually used as Cell selection and can be defined using Cell Editor in Query Designer. This situation produces no error messages, but the selection is not taken into account by OLAP.
If it is necessary, the selection definition can adjusted using the latest available version of Query Designer. The affected local selections can be accessed from the queries presented in the WHERE-USED (INFOCUBE/QUERY). The Restricted Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
In case, when a local selection is not used in any query or query components the recommended solution is to delete this selection using the corresponding delete procedure.
6.6 Local formulas of CKFs without records in RSZCALC table
Local formulas (DEFTP = 'FML') or Calculated Key Figures (DEFTP = 'CKF') should contain definition of the calculations in the table RSZCALC. When such definition is not found in the table RSZCALC the queries or query components which include those affected objects can not be generated or executed by OLAP. An attempt to generate such query returns the error message 'The (sub) formula XXX... is not available'.
The definitions of the affected formulas or Calculated Key Figures can be adjusted using the latest available version of Query Designer. The adjustment of a local formula is possible from the corresponding query listed presented in the program. The Calculated Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
In case, when a local formula is not used in any query or query components the recommended solution is to delete this formula using the corresponding delete procedure.
6.7 Variables without records in RSZGLOBV table
Variables (DEFTP = 'VAR') should exist in the table RSZGLOBV. The table RSZGLOBV contains all processing properties and definition of the variables. Query where such variables are used can not be executed without problems.
The repair procedure is not possible, because of missing definition. In case, when such variable is not used in any query, the recommended solution is to delete it from the system in order to avoid potential problems. If the affected variable is already used in other queries or query components, create an OSS message for SAP component BW-BEX-ET-QDEF. Further investigations and possible repair plan have to be created at SAP.
6.8 Queries without records in RSRREPDIR table
Queries (DEFTP = 'REP') should exist in the table RSRREPDIR. The table RSRREPDIR is a header table of generated reports and also a part of the database view V_REP_JOIN which provides data for the BEx Open/Save Dialogs.
A query which does not exist in the table RSRREPDIR is not accessible via RSRT transaction (error message 'GENUNIID not found') and not displayed in the Open/Save Dialogs of fronted applications.
The recommended solution is to delete such queries using the corresponding procedure provided in the program and similar to RSZDELETE.
In some cases the repair procedure is also possible. The success of the repair procedure depends upon the consistency of the affected query, the existence of a valid InfoProvider for this query and some other factors. For repair attempt create an OSS message for the SAP component BW-BEX-ET-QDEF.
hope this helps.

Transaction Code assignment for Query created in SQVI

Dear All,
Good morning I hope you are doing great...
Can any body help me out to assign transaction code for Query which was created through SQVI transaction.
Regards,
Murali.

Hi Murali Mohan
1>go to SQVI t code and enter your query name and press enter
2>In the menu path select Quick view--> additional functions-->Generate Program
3>After Generating the program In the menu path select Quick view--> additional functions-->Display report Name
4>Now in se38 enter the report name in Program field and execute
5>You will get the Initial Selection screen of the report . Go to Menu of System -->Status
6> Note down the Program name and Screen number
7>Go to SE93 and Create a Z tcode for the query, Enter the description and importantly you have to select the 2nd Option radio Button Program and Selection Screen (Report Transaction) and Press enter
8>In the next screen enter the Report name In Program field and enter the screen number
9>In the classification Section select Professional user Transaction
10>In GUI support section select all the options i.e SAPGUI for HTML,Java,Windows
and save
the system will ask for Package select your package if not there then select local object
now execute the Z tcode your report will run sucessfully
Regards
Vijay hebbal

Report to get current inspection status of material

Hi All,
In our company the Dynamic Modification Rule is active in task list for all materials. Is there any report to provide the present inspection status of incoming lot of those materials, whether they are skip or under inspection?
Or any table to get the same?
Thanks & Regds,
Ritesh

Hi Ritesh,
In QA33 itself u ill get the DMR details with respect to the inspection lot, if you want to develop
find here DMR related tables
QDBM Valuation mode
QDBMT Valuation Mode: Texts
QDDR Dynamic modification rule (header)
QDDRT Dynamic modification rule: texts
QDEP Allowed inspection severities
QDEPT Allowed Inspection Severities: Texts
QDPS Inspection stages for a dynamic modification rule
QDPST Inspection Stages: Texts
TQ39B QM : Activates reference for dyn. modification level
Thanks
Shiva

GRN With 2line items(material,batch same)one inspection lot for 2line items

Dear Experts
As and when we make a GRN with 2 line items and same batch number we enter no. of containers differently but only the number from the first line item is flowing into the Inspection lot origin.We are creating only one inspection lot for 2 line items as the batch number is same for the items.
1. In material master i have given 01 inspection type ( with control inslot.. Each material document,batch, storage location) :---
this is the reason system is creating only one inspection lot.
i am entering manually same batch number for 2line items...
Here my problem is ... while giving UD... SYSTEM IS PICKING ONLY FIRST LINE ITEM NO.OF CONTAINER... IT HAS TO BE BOTH LINE ITEMS CONTAINERS.... IT IS PICKING BOTH LINE ITEMS QUANTITY... NO.CONTAINER ONLY IT IS NOT PICKING....
Waitting for experts reply

Hi,
As per your query if you put in MM forums then you will get the reply immly.
Anil

Table for Inventory Status for Serialized materials

Hello,
Can anyone please provide the table name for finding out inventory status (i.e. unrestricted, Quality Inspection, Blocked) for serial numbers. I am trying to find out, in which inventory status does a particular serial# belonging to a particular material# is in?

Hello Azz:
Regarding the serial number status, you have to check the combination of three different tables:
EQUI - Equipment master data. In this table make note of the field 'Object number' (OBJNR), which is the primary key for:
JEST - Individual Object Status. This table contains the technical expression of the status in field 'Object status' (STAT), which is the primary key for:
TJ02 - System status. In this table you can find the texts for the system status in the fields TXT04 and TXT30.
Then, here you have some other tables which you might also need:
EQBS - Serial Number Stock Segment.
SER01 - Document Header for Serial Numbers for Delivery.
SER02 - Document Header for Serial Nos for Maint.Contract (SD Order).
SER03 - Document Header for Serial Numbers for Goods Movements.
SER04 - Document Header for Serial Numbers for Inspection Lot.
SER05 - Document Header for Serial Numbers for PP Order.
SER06 - Document Header for Serial Numbers for Handling Unit-Content.
SER07 - Document Header for Serial Numbers in Physical Inventory.
SER08 - Document Header for Purchase Order Item Serial Numbers.
I hope this helps!
Esther.

Inspection lot for inspection type 10,11,12

Hi,
My requrement is system should generate inspection lot at the time creation of sales order & before PGI.I assigned
inspection type 10,11,12 in QM view in material master.I have a quality planning with usage -3 & status -4.But when I am creating sales order & doing PGI system is not generating inspection lot.
manoj

Hi
check following QCC0>Qulity inspection>Inspection lot creation>Inspection at shipping>
Assign Inspection Lot Origin to Delivery Type
Assign agaist del type:
10 ; Outbound Delivery
11 :Delivery w/o Ref.
similerly for 12
Also
Assign Inspection Type to Delivery Category -->assign inspection lot origin & Inspection type for del catagory
Regards
Sujit

Muliple inspection plan for same material and same usage

Hi,
I need to create multiple inspection plans for same material with same usage.during the inspection lot creation i need to select any one inspection plan.
In standard SAP its not possible.Any user exits available for this..
Regards,
S.P.Selvathangam

Dear Selvathangam Palanisamy ,
My Dear Shayamal is absolutely correct and we are corrently using this SAP facility. You can create 'N' number of inspectio plans for a material and then whenever the inspection lot will created ( Thru a process order or Manual) then you will get the Inspection Lot Status 'CRTD' (Created mode) then you have to select your Inspection Task list manually by two way...
Either go to QA02 and then select it from the list of multiple plans.
Or you can directly go from QA32 ...select your inspection lot row and directly click on the Inspection Lot icon to go directly to the inspection lot window to slect the Task list.
Further there is no need to remove the Automatic Assignment from the QM View of the Material Master as if there is only one task List then system will automatically assign the TASK LIST, if you deselect it then you have to select in every case.
Thanks

Inspection results for more than one lot

How do i see inspection results for different lots of the same material together in a single screen. Is there any standard report or query available in SAP?
Prahlad

Dear Prahlad
You can see it in ways
1) Go to QS28. Input the plant and the mic and execute. You will get MIC details. Choose the MIC and click on Result history. A pop will appear Result history Limit Selection. In the Time Tab you can see inspection lot selection date From and To. Execute you will get the entire list of lots
3) Go to QA33 > result> Select the Mic> go Result historyhistory >In the Time Tab you can see inspection lot selection date From and To. Execute you will get the entire list of lots with all values and charts
4) standard reports such MCXD,QGP1 can be used
Hope this helps
Regards
gajesh

SQL Developer replacement for Query Builder?

Our developers use query builder to quickly develop sql code w/conditions, joins, where clauses, etc. I just installed release 2 of SQL Developer and am trying to figure out if this is a viable replacement for query builder. Is there a graphical "query builder" component as part of SQL Developer?

Barry, I would agree that it should be clean and easy to use. I started using Data Browser 2.0 and migrated to Query Builder 6.0.7.1.0 and while Query Builder is no longer it's own product it's integrated into Reports Developer 10g. The basic layout and operation has been consistent thru the life cycle and I would think you'd keep the "look and feel" consistent with what's currently available. (might simplify integrating it too). My biggest complaint with Query Builder 6.0.7 (se don't use the 10g version) is that it errors when opening a schema with more than 8192 objects. As an E-Business Suite 11.5.10 customer this is an issue for our developers when logging in as the standard APPS user.
So here would be my "wish list"
1. consistent look and feel with "older" versions of Browser/Query Builder
2. removal of 8192 object limitation
3. ability to open older .brw format files
Certainly more improvements would be possible by integrating with SQL Developer and would be welcomed - this wish list is coming from a user who has MANY .brw files in the older 6.0.7 format.

Person type and assignment status for terminated employee

Hi,
When I terminate an employee, is it possible to default the field "type" on "Person type and assignment status for terminated employee" section into another value? Its default values is: "Ex-Employee released".
Thank you.

Navigate to Work Structures -> Status and query for all rows with system status Terminated Assignment. select your required assignment status as Default. Untick the other default.

System status or user status for IDOC creation and processing for prod ord

All
I am creating IDOCs for production orders to send requirements to an external WM system for kitting execution.
I need to know whether there are any system statuses to notify me when an IDOC has been created,failed and processed. If not, how do I go about creating user defined statuses for these statuses.
Second question, which idocs should I use to confirm, teco and cancel the production orders from an external system?
Thanks
Evan

For the first part of your query refer to the technical forums.
For the second part - refer to Idoc - LOIPRO01, it has a segment for Order status, that should be of interest.
Attn Moderators
I think it would be better to move this thread to a technical forum, so the requester can get the most relevant information.

Configure another Inspection Type for Production Order

Hi QM Gurus,
I have one scenario, my client wants to have another inspection type for inspection lot origin goods receipt from production because they have this requirement that for some materials they need to have a status profile that will be active for inspection type standard 04. And there are also some materials from goods receipt from production that does not need status profile. Since the only thing that we could assign as specific status profile is to its inspection type. Hence, i need to create another inspection type for lot origin goods receipt from production aside from inspection type 04 that will create automatic inspection lots with different status profiles.I try this in configuration but no inspection lots has been made for new inspection type assigned to LOt origin 04 and also assigned in the material master inspection set-up. How will i do this???
Thanks.
Regards,
Matildo, Edsel
QM Consultant

Hello Edsel,
you can configure for example an inspection type 0401 and activate this inspection type for the inspection origin 04 in customizing. Please look at the following customizing items:
Transaction QCC3
-> Inspection Lot Creation
- Maintain Inspection Types
- Maintain Inspection Lot Origins and Assign Inspection Types
By activating the correspondent inspection type in the material master you can decide which inspection type is used. If you need both then you could think about using the exit QAAT0001 to assign the correspondent inspection type.
Regards
Isabelle

Component inspection status for query

Similar Messages

Maybe you are looking for