Difference between Existing QM system and Vendor QM system in QI info recor

In Quality info record, under inspection control tab, I find 2 options for certificate monitoring, one is Existing QM system and another one is Vendor's QM system, Please advice the difference between them.

hi dear,
There is no such difference, only he thing is when u developed or upload some new vendor based OM system which is valid from its industry type. Like in manufacuring it is strongly recomended that vendor is certified by some authorized agency like ISO, TUV Nord etc. so when u use this and configure it in ur sap system than u may change the setting and use Vendor QM system in Q-Info, while if is not there than u may use existing QM system of ur own company if u uploaded in SAP or u may keep it blank if not required.
if we use Vendor QM system than it is best practice to maintain QM procurement and related document like Certificate or Delievery assurance from vendor in MM02 ---> QM view.
I hope this short one cleares ur point.
regards
Shailendra Gaur
SAP-QM

Similar Messages

Difference between using new Date() and new Date(System.currentTimeMillis()

Hi All,
I have seen many open source api's where they are updating dates with the following code
new Date(System.currentTimeMillis())
when i print the new Date() it prints the same
what is the difference between using new Date() and new Date(System.currentTimeMillis()) ??
Thanks,
J.Kathir

when i print the new Date() it prints the same
It does because of backward compatability. This constructor exists in version 1.3.1 but not in newer versions.Really ? Please point me to where you read that.
API doc 1.5 : new Date() (still there, not even deprecated)
A quick look at the code for this constructor:    /**
     * Allocates a <code>Date</code> object and initializes it so that
     * it represents the time at which it was allocated, measured to the
     * nearest millisecond.
     * @see     java.lang.System#currentTimeMillis()
    public Date() {
        this(System.currentTimeMillis());
    }

Is there a performance difference between Automation Plug-ins and the scripting system?

We currently have a tool that, through the scripting system, merges and hides layers by layer groups, exports them, and then moves to the next layer group. There is some custom logic and channel merging that occasionally occurs in the merging of an individual layer group. These operations are occuring through the scripting system (actually, through C# making direct function calls through Photoshop), and there are some images where these operations take ~30-40 minutes to complete on very large images.
Is there a performance difference between doing the actions in this way as opposed to having these actions occur in an automation plug-in?
Thanks,

Thanks for the reply. I ended up just benchmarking the current implementation that we are using (which goes through DOM from all indications, I wasn't the original author of the code) and found that accessing each layer was taking upwards of 300 ms. I benchmarked iterating through the layers with PIUGetInfoByIndexIndex (in the Getter automation plug-in) and found that the first layer took ~300 ms, but the rest took ~1 ms. With that information, I decided that it was worthwhile rewriting the functionality in an Automation plug-in.

My ipad is barely charging - how can i tell the difference between iphone 6 charger and ipad

my ipad is barely charging - how can i tell the difference between iphone 6 charger and ipad

See the following page for info on all of Apple's chargers (you'll need to scroll down a bit on that page):
Charge the battery in your iPad - Apple Support

What is the difference between exists and in

hi all
if i have these queries
1- select ename from emp where ename in ( select ename from emp where empno=10)
and
2- select ename from emp where exists ( select ename from emp where empno=10)
what is the difference between exists and in is that only when i use in i have to bring the field name or what.... i mean in a complex SQL queries is it will give the same answer
Thanks

You get two entirely different result sets that may be the same. Haah! What do I mean by that.
SQL> select table_name from user_tables;
TABLE_NAME
BAR
FOO
2 rows selected.
SQL> select table_name from user_tables where table_name in (select table_name from user_tables where table_name = 'FOO');
TABLE_NAME
FOO
1 row selected.
SQL> select table_name from user_tables where exists(select table_name from user_tables where table_name = 'FOO');
TABLE_NAME
BAR
FOO
2 rows selected.So, why is this? the WHERE EXISTS means 'if the next is true', much like where 1=1 being always true and 1=2 being always false. In this case, where exists could be TRUE or FALSE, depending on the subquery.
WHERE EXISTS can be useful for something like testing if we have data, without actually having to return columns.
So, if you want to see if an employee exists you might say
SELECT 1 FROM DUAL WHERE EXISTS( select * from emp where empid = 10);
If there is a row in emp for empid=10, then you get back 1 from dual;
This is what I call an 'optimistic' lookup because the WHERE EXISTS ends as soon as there is a hit. It does not care how many - only that at least one exists. It is optimistic because it will continue processing the table lookup until either it hits or reaches the end of the table - for a non-indexed query.

Difference between exists and in operators in oracle?

what is difference between exists and in operators in oracle?
what is faster and why?

Malli wrote:
what is difference between exists and in operators in oracle?
what is faster and why?Is this a homework question?
Have you done any tests yourself to see which is faster?

In TCA, what is the difference between Item instance owner and System's own

Hi,
In TCA, what is the difference between Item instance owner and System's owner ?
thanks
siva

...can i make as many iweb websites as i want? ...and as many blogs as i want? ...i have never made one before....
....although, i do have my own small business and i do have a website that i paid a guy to make and also host....(which is a waste of $$$$ in my opinion as i think i can do a better job making one myself through iweb) ....
...anyways, i know it is splitting hairs but what exactly is the diff b/w a blog and a website ....i am under the impression that a blog is just a personal newsletter sort of thing,...?

What are differences between the target tablespace and the source tablespac

The IMPDP command create so manay errors. But the EXAMPLE tablespace is transported to the target database successfully. It seems that the transported tablespace is no difference with the source tablespace.
Why create so many errors?
How to avoid these errors?
What are differences between the target tablespace and the source tablespace?
Is this datapump action really successfull?
Thw following is the log output:
[oracle@hostp ~]$ impdp system/oracle dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
Import: Release 10.2.0.1.0 - Production on Sunday, 28 September, 2008 18:08:31
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Master table "SYSTEM"."SYS_IMPORT_TABLESPACE_01" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_TABLESPACE_01": system/******** dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
Processing object type TABLE_EXPORT/TABLE/TABLE
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "OE"."CUSTOMERS" ("CUSTOMER_ID" NUMBER(6,0), "CUST_FIRST_NAME" VARCHAR2(20) CONSTRAINT "CUST_FNAME_NN" NOT NULL ENABLE, "CUST_LAST_NAME" VARCHAR2(20) CONSTRAINT "CUST_LNAME_NN" NOT NULL ENABLE, "CUST_ADDRESS" "OE"."CUST_ADDRESS_TYP" , "PHONE_NUMBERS" "OE"."PHONE_LIST_TYP" , "NLS_LANGUAGE" VARCHAR2(3), "NLS_TERRITORY" VARCHAR2(30), "CREDIT_LIMIT" NUMBER(9,2), "CUST_EMAIL" VARCHAR2(30), "ACCOUNT_MGR_ID" NU
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "IX"."ORDERS_QUEUETABLE" ("Q_NAME" VARCHAR2(30), "MSGID" RAW(16), "CORRID" VARCHAR2(128), "PRIORITY" NUMBER, "STATE" NUMBER, "DELAY" TIMESTAMP (6), "EXPIRATION" NUMBER, "TIME_MANAGER_INFO" TIMESTAMP (6), "LOCAL_ORDER_NO" NUMBER, "CHAIN_NO" NUMBER, "CSCN" NUMBER, "DSCN" NUMBER, "ENQ_TIME" TIMESTAMP (6), "ENQ_UID" VARCHAR2(30), "ENQ_TID" VARCHAR2(30), "DEQ_TIME" TIMESTAMP (6), "DEQ_UID" VARCHAR2(30), "DEQ_
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
. . imported "SH"."CUSTOMERS" 9.850 MB 55500 rows
. . imported "SH"."SUPPLEMENTARY_DEMOGRAPHICS" 695.9 KB 4500 rows
. . imported "OE"."PRODUCT_DESCRIPTIONS" 2.379 MB 8640 rows
. . imported "SH"."SALES":"SALES_Q4_2001" 2.257 MB 69749 rows
. . imported "SH"."SALES":"SALES_Q1_1999" 2.070 MB 64186 rows
. . imported "SH"."SALES":"SALES_Q3_2001" 2.129 MB 65769 rows
. . imported "SH"."SALES":"SALES_Q1_2000" 2.011 MB 62197 rows
. . imported "SH"."SALES":"SALES_Q1_2001" 1.964 MB 60608 rows
. . imported "SH"."SALES":"SALES_Q2_2001" 2.050 MB 63292 rows
. . imported "SH"."SALES":"SALES_Q3_1999" 2.166 MB 67138 rows
Processing object type TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."REGIONS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."REGIONS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."COUNTRIES" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."COUNTRIES" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."LOCATIONS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."LOCATIONS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."DEPARTMENTS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."DEPARTMENTS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOBS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOBS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."EMPLOYEES" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."EMPLOYEES" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOB_HISTORY" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOB_HISTORY" TO "EXAM_03"
ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
ORA-39112: Dependent object type INDEX:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_LNAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_EMAIL_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"PM"."PRINTMEDIA_PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_CREDIT_LIMIT_MAX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_ID_MIN" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"PM"."PRINTMEDIA__PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type CONSTRAINT:"IX"."SYS_C005192" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUSTOMERS_PK" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_LNAME_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_EMAIL_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"PM"."PRINTMEDIA_PK" creation failed
Processing object type TABLE_EXPORT/TABLE/COMMENT
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
ORA-39112: Dependent object type REF_CONSTRAINT:"OE"."CUSTOMERS_ACCOUNT_MANAGER_FK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39083: Object type REF_CONSTRAINT failed to create with error:
ORA-00942: table or view does not exist
Failing sql is:
ALTER TABLE "OE"."ORDERS" ADD CONSTRAINT "ORDERS_CUSTOMER_ID_FK" FOREIGN KEY ("CUSTOMER_ID") REFERENCES "OE"."CUSTOMERS" ("CUSTOMER_ID") ON DELETE SET NULL ENABLE
ORA-39112: Dependent object type REF_CONSTRAINT:"PM"."PRINTMEDIA_FK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
Processing object type TABLE_EXPORT/TABLE/TRIGGER
ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
Processing object type TABLE_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
ORA-39112: Dependent object type INDEX:"OE"."CUST_UPPER_NAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_UPPER_NAME_IX" creation failed
Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCACT_INSTANCE
ORA-39112: Dependent object type PROCACT_INSTANCE skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39083: Object type PROCACT_INSTANCE failed to create with error:
ORA-01403: no data found
ORA-01403: no data found
Failing sql is:
BEGIN
SYS.DBMS_AQ_IMP_INTERNAL.IMPORT_SIGNATURE_TABLE('AQ$_ORDERS_QUEUETABLE_G');COMMIT; END;
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCDEPOBJ
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_V" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_N" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_R" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_E" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Job "SYSTEM"."SYS_IMPORT_TABLESPACE_01" completed with 63 error(s) at 18:09:14

Short of trying to then reverse-engineer the objects that are in the dump file (I believe Data Pump export files contain some XML representations of DDL in addition to various binary bits, making it potentially possible to try to scan the dump file for the object definitions), I would tend to assume that the export didn't include those type definitions.
Since it looks like you're trying to set up the sample schemas, is there a reason that you wouldn't just run the sample schema setup scripts on the destination database? Why are you using Data Pump in the first place?
Justin

Differences between MDM 3.0 and MDM 5.5?

Hi,
Can anybody tell, what are the differences between MDM 3.0 and MDM 5.5?
I heard that, there are lot and lot of changes...
Thanks for your reply,
regrads,
cg

We can look at differences in more than one way:
1. Technology wise
MDM5.5 is developed in C++ & runs on a C++ engine as compared to MDM 3.0 which runs under WAS
However MDM 5.5 is integrated with NW largely, though it can & is planned to be improved further
2. Product Catalog Management
MDM 5.5 has rich PCM capabilities which did not exist in MDM 3.0
3. Other additional capabilities in 5.5
Multilingual support
Syndication of data to XI or file system
Lean, R/3 Idoc based model for supplier, customer, material, employee
4. Ease of installation and usage is a also an advantage of 5.5
You can read Nitza Levi's blog on MDM home page for more details

Re: DIfference between Schemas, PCRS' FUnctions and Operations

Dear SAPExperts,
Can anybody pls tell me what is difference between Schemas, PCRS' Functions and Operations.
Thanx in advance
Regards
Aniruddha

Hi Aniruddha
When the payroll driver is executed (for ex: PC00_M40_CALC for INDIA is executed) the schema IN00 (standard schema) is executed and it calls certain functions (functions may use Rules. Rules contain Operation) and also subschemas.
Functions could be of four types
1. Performing some payroll computations (E.g. INEPF function calculates the PF amount of an employee during payroll run)
2. Calling rules (E.g. P0045 function calls a rule INLN to compute the loan details of a personnel number).
3. Getting data from Infotypes (E.g. P0581 will get the data from Infotype-581 for payroll processing).
4. For some decisions. (E.g. IF & ENDIF function is used to execute as per the true and false decisions) etc.
When the PY is executed SAP uses lot of Internal Tables to store data and also provides data to other internal tables.
The read and change access to Internal Tables is enabled using functions that are executed in a personnel calculation schema and using operations that are executed in personnel calculation rules.
The following is just an attempt to provide some info on how Functions are processed during the PY Run. For ex: (functionality of subschema XIN0 and INBD)
1. INITIALIZATION OF PAYROLL: When the Payroll is executed first the subschema XIN0 is called,   This subschema comprises the following main steps:
I.     Specify program type (payroll or evaluation)
II.     Set switch for database updates (YES/NO) all database updates are controlled via this switch (otherwise simulation)
III.     Only infotypes from the HR master record which apply to the selected personnel number are read.
IV.     All Time Management infotypes are imported.
V.     Specify check against control record PA03 (test or live).
2. READ BASIC DATA: Once the Initialization of Payroll is successful, the subschema INBD is called. This subschema reads the Basic data of an employee who is there in the Payroll execution. Basic Data includes, determining Employee Name, Reading Work Center/Basic Pay Data, Setting Financial Year Dates and Allowance Grouping Tables, Reading Previous Employment Tax Details, Reading Housing (HRA/CLA/COA), Reading Exemptions, Reading Income from Other Sources, Reading Section 80 Deductions, Reading Investment Details (Sec 88), Reading Provident Fund Contributions, Reading Other Statutory Deductions, Reading Car and Conveyance, Reading Long Term Reimbursements, Read ID Details. Function GON checks whether all the master data has been imported, no further processing of schema will occur unless certain data is present.
The Subschema INBD calls the following functions in order to read the Basic Data:
ENAME :
Function ENAME reads the last valid name of the employee in the payroll period. The formatting used for the country in question is used when displaying this name.
WPBP
If an employee receives a pay increase within a payroll period, the Basic Pay infotype (0008) is changed and delimited as of a specific date. Two data records exist for one payroll period.
During payroll, the system writes the Basic Pay wage type to the results table with two different indicators. These split indicators are a link to the WPBP table that contains the relevant values. The system takes into consideration both data records for the corresponding partial periods when calculating remuneration.
ININI
P0580
P0581
P0582
P0584
P0585
P0586
P0587
P0588
P0583
P0590
P185I
GON :
                Function GON checks whether all the master data has been imported. No further processing of the schema will occur unless certain data is present. Checking procedures vary from country to country. There must always, however, be a work center (P007).
[Def. of Functions, Rules and Operations (copied from Raju's answer)
Schema is a collection of functions
A Rule is a collection of operations.
An operation is a very basic piece of logic that is used, mostly, to manipulate wage types
Best Regards
Reddy

Difference between cost component structure and cost component split

can anyone explain me the difference between cost component structure and cost component split with simple example
thanks
santosh

Hi ,
cost component structure
Definition
Number that identifies the structure.
Use
In Product Cost Controlling, the cost component structure determines how the results of material costing are updated. The cost component structure groups the costs for each material according to cost component (such as material costs, internal activities, external activities, and overhead). If the material is used in the production of another material, the cost component split (which breaks down the costs according to material costs, internal activities, external activities, overhead, and so forth) remains in the system when the costs are rolled up.
In the cost component split, you also define the following for material costing:
Which part of the costs are fixed costs
Which costs are
cost of goods manufactured and what are sales and administration costs
Which costs are relevant for stock valuation, commercial inventory valuation and tax inventory valuation
When the cost component structure is assigned to the organizational units, you can specify that two cost component splits are created:
Main cost component split
This is the principal cost component split, meaning that it is used in the standard cost estimate, which can be used to update the material master. The main cost component split can be a cost component split for cost of goods manufactured or a primary cost component split.
Auxiliary cost component split
This can exist in addition to the main cost component split, and is not used in the standard cost estimate. It can be used for analysis purposes, in that it can be displayed with the cost estimate and passed on to Profitability Analysis.
In Cost Center Accounting, the cost component structure determines how the results of the activity price calculation are updated. The cost component structure groups the costs for each activity type of the cost center according to components (such as material costs and labor costs). If an internal activity allocation is carried out, the cost component split (which breaks down the costs according to material, labor costs, and so forth) is retained at cost rollup.
If the cost component split is not to be retained, you can create a switching structure for the cost component structure for Cost Center Accounting. In the switching structure, you specify which sender cost component goes into which receiver cost component.
<b>require a cost component structure to calculate prices using cost component split.</b>
For each cost component structure you define a component such as energy, personnel, or raw materials. The components combine all costs occuring for a particular cost element area. In this way, you ensure greater cost transparency in activity price calculation when putting together the activity type prices - for example, it becomes easier to find how much of the activity price is taken up by the material costs.
In activity allocation, the cost component structure remains constant, meaning that the receiver takes on the sender cost elements and that the allocated costs are posted in the same cost components in the receiver as in the sender.
A cost component structure can have a maximum of 40 defined cost components.
Cost components are assigned to cost elements. You thereby determine which cost elements go to which rows in the structure, and how these components are updated in price calculation.
Hope ths helps
Please rewad points
Sunil

Difference between BSI 8.0 and 8.0G

Hello All
Can someone tell me the Difference between BSI 8.0 and 8.0G?
Thanks

Charlene :
Below is the cut and paste message from BSI on the reason of BSI 80g to be used on first payroll on 2008. In short, this version contains certain critical tax change/calculation not in lower version of BSI 80 (e.g. e and f). If you already upgraded to BSI 80, then this is just a cyclic update (not as bad as from 70 to 80) plus tubs up to 68 (to include PA tax changes).
Rgds.
Please note this is a Mandatory cyclic upgrade, due to BSI modifications to benefit plan and earning type data layout information, and to accommodate additional Pennsylvania Local Services Tax (LST) changes effective January 1, 2008. Pennsylvania Local Services Tax (LST) rates are scheduled to be published by the Department of Community and Economic Development (DCED) on December 15, 2007. BSI will issue the pertinent data updates shortly thereafter. Due to the anticipated volume of changes, we expect to issue the data updates over several TUBs.
This cyclic upgrade must be installed as soon as possible, prior to running your first 2008 payroll, in order to keep your TaxFactory system current. Please check with your vendor for certification information.

Difference between a positive time and negative time management.Explain with screenshots.

Hi gurus!
I would like to know the difference between Positive time management and negative time management.
thx & regards,
raju

Hi Nagaraju,
I am adding more information..
Whether or not an employee is on positive or negative time is determined by the time management status on IT0007. Status 1 or 2 = positive time; status 9 = negative time.
In a standard system, positive time recording means the employee is required to record time (absence or attendance) for any day on which he is scheduled to work according to his generated work schedule. Negative time recording means an employee does not need to record time unless he has an exception to his normal working time; so absences are typically recorded as well as overtime or time work on days for which the employee is not scheduled to work.
Schema TM00 is used to process positive time employees for whom clock times are entered; that is, every record has a start and end time.
Schema TM04 processes both positive and negative time employees. The key distinction between TM00 and TM04 is TM04 does not require start and end times on every entry. Records with start and end times cna be processed in TM04. However, the records do not require these entries.
In TM04 you will see code using IF, ELSE, ENDIF statements during the import process to separate the import of time data for positive and negative time employees.
Positive time employees use the following data import statements in the schema:
P2011 Import IT2011 records to TIP; regardless of whether the EE has IT2011, load the work schedule to TZP. If no IT2011 record exists, TIP is empty.
P2001 Load absences
P2002 Load attendances
Negative time employees use the following data import statements:
P2000 This is the critical difference between positive and negative employees. P2000 loads the daily work schedule to the TIP table as if the employee workede; that is, if the employee is scheduled to work from 8:00 to 17:00, this record will now appear on TIP. The work schedule details are also added to TZP.
P2001 Load absences -- to pick up exceptions to planned working time
P2002 Load attendances -- again to pick up exceptions, special costing information, overtime, alternate payments, premiums or any other variation from normal schedule work.
So if you want to determine if you are using positive or negative time, check the time management status on the employees.
Regards
Siva

Difference between SAP 4.7 and ECC 5.0

hi frnds
.what is the difference between SAP 4.7 and ECC 5.0?
regards

Hi,
Following are the basic differences as far as MM Module is concerned
Pickup list - Batch where-used list display in transaction MB56
u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
Usability enhancements for transaction MIGO for the posting of goods movements
u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
u2022 User changes the default values in the menu path "Settings -> Default Values."
u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
Goods receipt
Goods issue
Transfer posting
Remove from storage
u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
New report : display list of invoice documents (MIR5)
u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
u2022 In the output list, the report shows both posted and held invoices.
u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
Requirement prioritizations in materials management
u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
Mass maintenance of outline agreements
The following two transactions available:
u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
Commitment plan for purchase contracts
u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
u2022 This commitment plan itself can have any number of items.
u2022 User can define a value and a validity date for each commitment plan item.
u2022 This enables user to pre plan different values for different periods of time.
u2022 The software generates an earmarked fund document for a defined commitment plan item.
u2022 This earmarked funds document can in turn contain several different items with different account assignments.
u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
u2022 Account assignment to a different account assignment object is then no longer allowed.
Availability check in "Enjoy purchase order and requisition"
u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
u2022 Two settings are possible with availability check:
Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
Delivery proposal - Full confirmation
External services: putting service items in the purchase order on hold (changed)
User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
Customizing transactions OX18 replaced by view
The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
Goods receipt: new movement types in inventory management
The following new movement types are available in inventory management:
107: Goods receipt to valuated goods receipt blocked stock
109: Goods receipt from valuated goods receipt blocked stock
Prepayment of invoices
This functionality is characterized as follows:
u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
u2022 When the software posts invoices, it continues to execute the standard checks.
u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
Purchasing accounting information to the former SAP Business Information Warehouse
u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
u2022 Functionality for report RMMR1MRS is enhanced.
u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
u2022 To do so, set the relevant indicator on the initial screen of the report.
Parking service items
It is now possible to put service orders without errors or with commitment errors on hold.
Report MB5B : Stock on Posting Date
u2022 This Report is available with u201CNon-Hierarchyu201D display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
u2022 This functionality is not available in Release 4.7.
Stock Transfer Between Storage Locations
u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
u2022 As a result of which user can input issuing storage location with supplying plant.
u2022 Facility of using different delivery types for different issuing storage locations is available.
u2022 Shipping Point data can also be determined based on the issuing storage location
Regards
Priyanka.P
AWARD IF HELPFULL

What is the difference between generate partner profile and creat partner

What is the difference between generate partner profile and creat partner profile ?

Create Partner ProfilesAlthough partner profiles are usually created automatically, because of the unusual inbound and outbound profiles needed on the same system, the manual generation of certain profiles is required.
The following subsections describe the partner profile settings for the standard client (assumed here to be ALExxxCyyy), as well as for the corresponding dummy client (assumed to be DUMxxxCyyy). The dummy client partner profiles should have been generated by the automatic generation process completed previously. Nevertheless, these should be checked to ensure that all profiles exist.
Generation of Partner Profiles
The following messages should be added to the 4xx-ORDR model for ALExxxCyyy to DUMxxxCyyy on the reference client:
ORDERS
ORDCHG
ZINVRV
ORDRSP
INVOIC
FIDCMT
The partner profiles should first be generated using the standard auto-generation procedure on the reference client (for SYNCH messages to be created).
This model should now be distributed to the both ALExxxCyyy and DUMxxxCyyy.
The partner profiles should now be generated on the client being configured (i.e. yyy) using the auto-generation procedure defined in the standard ALE configuration procedures.
Generate partner profiles for sending system. (Can only do this if at least 1 message type exists against the sending system's LS). This automatically generates the port if the LS and RFC name are the same.
generate partner profiles tcode BD82
creating partner profiles tcode WE20
 There are two methods for maintaining the partner profile:
 Maintain partner profile manually:
To navigate to the partner profile in the sender system, choose Partner profile -> Partner type of Logical System and click on the required Target system. Under Outbound parameters, choose the Create outbound parameters icon, and enter the values for the outbound parameters according to the slide Sender: Partner Profile (outbound).
To navigate to the partner profile in the sender system, choose Partner profile -> Partner type of Logical System and click on the required Sending system. Under Inbound parameters, choose the Create inbound parameters icon and enter the values for the inbound parameters according to the slide Sender: Partner Profile (inbound).
 Generate partner profile:
Prerequisite: The current distribution model is distributed to all participating systems.
In the sender system, choose: Generate Partner Profile, then check the result in the partner profile (outbound)
In the sender system, choose: Generate Partner Profile, then check the result in the partner profile (inbound)
Regards
Vasu

Difference between Existing QM system and Vendor QM system in QI info recor

Similar Messages

Maybe you are looking for