Difference between Production Supply Area and a Storage Location

Hello Experts,
Basic question but wanted to get more clarity on the concept as i never worked on the PSA
Can someone tell me the exact difference between PSA and a SL. I understand PSA is a Kanban, WM and SL is an IM concept. Can a work center have a storage location assigned or just a PSA? Can a GI be done from PSA or just from a storage location.

Hello
The production supply area is a master data used by WM, while the storage location is used by MM-IM.
Check this link for details:
Production Supply Area - Warehouse Management System (WMS) - SAP Library
The goods issue is done with reference to the storage location
It is possible to assigne a storage location to a production supply area and assign the production supply area to the work center.
BR
Caetano

Similar Messages

Material staging in production with IM and WM storage locations

Hello,
I have the following situation at hand in a Client.
They use Process Orders and want to do material staging of the components.
The Production Supply área is an IM managed storage location but the storage location of the components is WM managed.
The staging should take place as pick parts (control cycle) transfering the components from the WM storage location to the IM production Storage location.
Im not sure we need to use Deliveries instead of Transfer Requirements.
Is this escenario posible and if so, how to configure it.
Thanks for any reply.
Aart

Aart,
For Transfer requirement creation for production order components WM staging please follow below steps.
1.Activate PP interface in Warehouse number control for PP interface in Logistic execution.
2.You need to assign WM replenishment movement type 319 against the production supply storage type.
3.In production scheduling profile all necessary WM TR/TO configuration to be done based on your requirement.
4.Create PSA in PK05.
5.Create Control cycle in LPK1.
6.Assign the PSA to production work centers.
With above settings once production order is released TR gets created which could be converted to TO manually or automatically for further process.
Br
KK

What is difference between "Product Recovery Media" and "Recovery Media"?

Both of the above are options in my ThinkVantage Folder. I asked Lenovo (Atlanta?) and uhm...they did not know either.
....And will either option give me the option of doing a clean Vista Ultimate install minus bloatware?
thks
J
Message Edited by jc321 on 11-13-2008 03:02 PM
Message Edited by jc321 on 11-13-2008 03:03 PM
Moderator Note; please update your profile with your correct country location as per the forum rules. Products, options and services vary from market to market. Knowing your location helps us help you
Message Edited by andyP on 11-14-2008 12:25 AM
Solved!
Go to Solution.

Got it - thanks.
For such a critical function one would think they would make that a tad more clear. You can also click on the Lenovo Partition. It will prompt you to create Recovery Media there as well. The contents of which match neither the Product Recovery Media nor the Recovery Media.

Replenishement directly from external supplier to production supply area

Hi Experts
I'm new in WM,
We have a big tanks for oil which will be used by the production as a component during the production process, these tanks is in the PSA "Production supply Area" and the supplier provide the oil directly to PSA ( not throug the Warehouse) so these tanks are under the production control.
we need to implement this process in SAP.
we need the stept by step implementation of that request
your support is highly recommanded for us
Many thanks in advance
Olfa

There are many ways to do your requirement. One among them is, Implement KANBAN Process using External Replenishment.
Evaluate options using PK01 .. External proc.
Regards,
Sathish

Production supply area (PSA) and supply area

Hi,
Is there any difference between supply area and Production supply area. it woul be good if you could explain me the difference.
Thanks,
Maxx

Both are same
Production Supply Area is the link between Warehosue Management and Production function.
Production supply areas (PSAs) are used for material replenishment and are situated directly on the shop floor in the production department. The supply area groups work centers near production storage bins based on the material staging methods. You need to enter the PSA in the work center master data.
http://help.sap.com/saphelp_46c/helpdata/en/c6/f8412f4afa11d182b90000e829fbfe/frameset.htm
Hope this helps.
An area on the shop floor where material is provided that can be directly used for production.
The supply area is used, for example, in KANBAN production control and for material staging using Warehouse Management (WM).
Proposed Supply Area in Material Master Record
The supply area is used as an interim storage area on the shop floor
     which is used to provide materials directly at the production line.
The proposed supply area is mainly used for KANBAN materials that are
     only or usually provided at one supply area in a plant. Here, this supply
     area can be easily saved in the system.
The proposed supply area is used, for example, to determine the supply
     area for the dependent requirements of a material.
     The supply area in the dependent requirements of a material is required:
     o to enable the system to calculate the KANBAN control cycles
        automatically
     o to enable you to select requirements in the pull list with reference
        to a supply area

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 Product Version SAP ERP 2005 and SAP ECC 6.0

Hello Guys,
I have to setup an new XI interface between two R/3 system. During Integration Scenario setup you have to select under Application Component Type the Product version for the R/3 systems.
Now, i am able to select SAP ERP 2005 or SAP ECC 6.0 from menu
Could someone tell me the differences between SAP ERP 2005 and SAP ECC 6.0. Both are listed as Product Versions.
Thanks in advance!
Jochen

SAP ECC 6.0 is latest version 2005 is last year version . as you are intergatin between 2 . you need select accordingly our source and target.
let me know you still require any doubt
Thanks
Sreeram
Message was edited by:
Sreeram Reddy

What are the major differences between the 4.7 and ECC5 or 6   ?

Hi Abapers,
                        Can anyb one answer this question ....
what are the major differences between the 4.7 and ECC5 or 6    ?
Thank's,
Siri

Tan,
we have solution for this question on previous pages.

What are the OS differences between mini, mini server and XServe?

Hi,
Apart from cpu speed disk size and memory,
what are the differences between the mac mini and the mini server?
What, if any, are the differences in the OS, software tools etc?
Also, what are the differences between the OS in the mini, mini server
and the XServe (apart from of course cpu cores etc)?
Thanks

Thanks.
Is it safe to say that these two pages list
all the differences?
http://www.apple.com/macosx/specs.html
http://www.apple.com/server/macosx/specs.html
Or is there any doc from Apple that lists the differences?
Thanks.

Difference between Groups books/IFRS and Local Stats Depreciation Areas

Hi
We created assets with difference useful life between Groups and Stats of which the asset depreciation difference between two dep areas is posted in to seperate GL account starts with "S" used for local stats purpose. Any idea how to avoid this difference getting posted to other stats GL account.
We also tried to have same useful life between dep areas. But still i can see depreciation difference is getting posted in dep area 30.
Kindly help.
REgards,
Hari

Hi Hari
Welcome to SDN.. This is standard behaviour....
If you have 2 dep areas posting to FI, then you need to create a 3rd depre area as Delta Dep Area which manages the differential posting between Dep Area 01 and Parallel Dep area
Only solution to avoid this is to have the Parallel Dep Area as STatistical Dep Area i.e. It should not post to FI (Indicator 0 in OADB)
br, Ajay M

What is the difference between WTR1 stock price and Price,some time both are zero?

what is the difference between WTR1 stock price and Price,some time both are zero?
please advice

Hi,
Are you referring these two field in WTR1 table? If yes,
(Figure 1 There is no price defined and received with zero price)
1. Based on price list, this info price will be updated. If there is no price, this field is zero
2. If you receive any item without price (for GRPO with zero price), then field is zero
3. If you receive item with price, based on quantity, the moving average price will be updates at item cost.
Thanks & Regards,
Nagarajan

What are the differences between a trial version and a licensed copy of RoboHelp?

What are the differences between a trial version and a licensed copy of RoboHelp? How is original Robohelp software useful compared to the evaluation version (freely downloaded software)
Thanks.

Welcome to the forum.
The only difference should be that the trial is limited to 30 days use. All functionality works and nothing is watermarked Trial or suchlike.
The trial of the standalone version allows you to link to FrameMaker documents. It should not and that feature will be disabled if you proceed with the full version. Other than the time limitation, that is the only difference.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Difference between production version and routing

hello pp experts,
                        why do we create production version, and what's the difference between production version and routing?

Dear sarfaraz lodhi ,
Production version is a combination of BOM & Routing in the case of Discrete Manufacturing and it's a
combination of BOM & Rotuing/Rate Routing in the case of Repetitive Manufacturing.
Created either through MM02 by selecting MRP4 view or else through C223
A production version determines the various production techniques that can be used to produce a material.
It defines the following information:
·        Alternative BOM for a BOM explosion
·        Task list type, task list group, and group counter for assignment to task lists
·        Lot-size restrictions and period of validity
A material can have one or more production versions.
Routing contains the set of operation that's required for producing a product either a HALB - Semi-
Finished product or else a FERT - Finished Product.
The T code for creating Routing is CA01.
Regards
Mangalraj.S
Edited by: Mangalraj.S on Sep 24, 2008 10:27 AM

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

Errror : production supply area not available fieldin work center .

HI
   hi friends
        i want to maintain production supply area in work centre...
        production supply area means storage location??
      i have a confusion between storage location and production supply area
pls suggest me where i missed the setting
with regards
dinesh

Production supply area is not a storage location. It is linked to one, but you may have more than one supply area per storage location.
Supply areas are used in KANBAN processes, and I think that also in WM-PP interface.

Difference between Production Supply Area and a Storage Location

Similar Messages

Maybe you are looking for