Transaction CL02
im getting "No batch input data for screen SAPLCLMO 0100" when i tried to upload my file through LSMW (CL02). in recording i did not find the error(not actually error) but i found it wen i was running batch input session. If i press enter it ll proceed to next screen. help me in removing that prompt.
SAP has defined import methods to create and change classes.:
batch input object 0140 with method 0000
idoc method CLFMAS
There is no need to create own recordings.
Similar Messages
-
when i tried to create legacy for batch input in tx CL02, im getting error as "No batch input data for screen SAPLCLMO 0100". I tried recording thrice, im getting the same error. all other fields are working fine. help me out resolving this error.
there is no need to do a recording as SAP has developed standard import methods for this activityin LSMW:
e.g.
standard batch input
Object 0140 Class
Method 0000
Programmname RCCLBI01
and IDOC method
message type CLMAS
basis type CLFMAS02
now to the error you receive 'No batch input data for screen SAPLCLMO 0100'
in SE51 you can enter SAPLCLMO and dynpro 0100 and display the layout.
you will see that this is the initial screen of transaction CL02.
did you miss to define the fields? did you miss to do the field mapping and move values to the fields? -
Recreate cl02 with limited F4 help
i need to recreate CL02 and cL01 transaction so that the F4 help contains limited class types only.
kindly tell me how to proceed and also i need to restrict an object so that not all the users get access
to this zclo1 .Hi,
Let try this:
1. Create one customized program with BDC, declare your search help in the program.
2. Assign customized tcode to it. E.g. ZCL02
3. Remove authorization from your users' roles/profile, don't let them access to standard tcode CL01 and CL02
4. Assign authorization to your users' roles/profile, let them access to your customized tcode ZCL01 and ZCL02.
Example:
REPORT ZTEST.
DATA: BEGIN OF BDCDATA OCCURS 30.
INCLUDE STRUCTURE BDCDATA.
DATA: END OF BDCDATA.
DATA: BDCTAB LIKE BDCDATA OCCURS 100 WITH HEADER LINE.
DATA: BEGIN OF MESSAGE OCCURS 0,
MSG TYPE BAPI_MSG,
END OF MESSAGE.
DATA: I_BDCMSGCOLL TYPE STANDARD TABLE OF BDCMSGCOLL WITH NON-UNIQUE KEY TCODE INITIAL SIZE 0,
WA_BDCMSGCOLL TYPE BDCMSGCOLL.
PARAMETERS: P_CLASS TYPE CHAR18,
P_KLART TYPE CHAR3.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_CLASS.
* <--write your search help here-->
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_KLART.
* <--write your search help here-->
START-OF-SELECTION.
PERFORM BDC_PROCESS.
SORT I_BDCMSGCOLL BY MSGTYP.
CALL TRANSACTION 'CL02' USING BDCDATA
MODE 'N' "'N' for nothing 'A' Display all
UPDATE 'S'
MESSAGES INTO I_BDCMSGCOLL. " Return error message
READ TABLE I_BDCMSGCOLL INTO WA_BDCMSGCOLL WITH KEY MSGTYP = 'E' BINARY SEARCH.
IF SY-SUBRC EQ 0.
MESSAGE ID WA_BDCMSGCOLL-MSGID TYPE WA_BDCMSGCOLL-MSGTYP NUMBER WA_BDCMSGCOLL-MSGNR
WITH WA_BDCMSGCOLL-MSGV1 WA_BDCMSGCOLL-MSGV2 WA_BDCMSGCOLL-MSGV3 WA_BDCMSGCOLL-MSGV4.
ELSE.
CALL TRANSACTION 'CL02' USING BDCDATA
MODE 'E' "'N' for nothing 'A' Display all
UPDATE 'S'
MESSAGES INTO I_BDCMSGCOLL. " Return error message
ENDIF.
REFRESH BDCDATA.
* Process *
FORM BDC_PROCESS.
PERFORM BDC_DYNPRO USING 'SAPLCLMO' '0100'.
PERFORM BDC_FIELD USING 'RMCLM-CLASS' P_CLASS .
PERFORM BDC_FIELD USING 'RMCLM-KLART' P_KLART.
PERFORM BDC_DYNPRO USING 'SAPLCLMO' '0100'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '/00'.
ENDFORM. "BDC_PROCESS
* Start new screen *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM. "BDC_DYNPRO
* Insert field *
FORM BDC_FIELD USING FNAM FVAL.
CLEAR BDCDATA.
BDCDATA-FNAM = FNAM.
BDCDATA-FVAL = FVAL.
APPEND BDCDATA.
ENDFORM. "BDC_FIELD -
How to add new value in Classification under General tab via MM02.
Hello Experts,
I've a requirement where I need to add a new material variant configuration value via MM02 as highlighted below. I've also attached the screen shot of CL02, the two characteristics which I need to add (highlighted in red).
Can please anybody tell me the steps to add value in Classification under General tab via MM02.
Many thanks in advance.zero cool,
Use transaction CL02 , open class in PCL_222_PURO_BOX with class type 300
add characterstic
PCH_COSTING_WGT_DETERM
PCH_COSTING_WGT_A_DETERM
save it.
Now use MM02 and go to classification view , now you would be able to see these characterstic there.
Check and come back.
Thanks
Ritesh -
LSMW for Object 140 (Class) - Using Batch
Hi All,
I am trying to use LSMW to change status for an already defined class. I am using object 0140 (program RCCLBI01), but when doing the data transfer, it keeps trying to do it as a create class (tcode CL01).
In the source relations for structure BIKLA, I see the tcode field. I changed this default to CL02, however I get an error - that transaction CL02 is not supported by this program.
Pls advise if you have worked on such a scenario before.
It appears to me that the next option is try BAPI/ ALE. Let me know if anyone has tried this earlier, as I am going to give it my first shot now.
Thanks!!
LizHi, You can create a small recording as a second step to change the status of a class.
Hope this helps.
Best Regards, Murugesh -
Material select views in lsmw??
Hi Guru:
I am encountering a strange question that I selected some tab when creating material in mm01and I ticked create views selected check box,but when I am going to lsmw and trying to record transaction,the system asked me to select tab views again although I had set it in mm01,so it will be causing the issue when I am do recording transaction in lsmw,help!!!!hii
This LSMW shows how to mass load material master characteristics. The LSMW used is exactly the same as what was used to load release procedure values. Input file is obviously different.
Material Master classification can be used to store additional information against a material master. Example: if it is finished products you may want to store: brand, pack, etc. If it is maintenance materials, you may want to store: size of item, grouping, etc.
Before loading the values (per material), you first need to create the fields (characteristics) and group them together in a class. This is done with following transaction codes:
u2022 Create class u2013 transaction CL02
u2022 Create characteristic(s)s u2013 transaction CT04
u2022 Assign characteristic(s) to class - transaction CL02
No screen shots about CL02 and CT04 u2013 you should be be able to get that right.
Material characteristic values can be viewed from a few places:
u2022 MM03 Display material and select characteristic view
u2022 CL20N Specify class type 001 and material master number
u2022 CL24N Specify class name and class type (001 in this case) -
Total Solids% in Recipe Management
Hi All,
I have 2 queries regarding the properties tree in Specfication management
1. we are unable to add property called ' Total Solids% ' in the property trees
' Trem Card ' or ' RM standrad Property Tree ' in the Substance maintanance ...
2. Even after adding some other properties in the property tree we are not able to do value assingment for the properties, we are getting the following message..
" Customizing for this value assignment type was not yet generated "
SAP ECC 6.0 which is newly installed
Thanks & regards
Yasar
Message was edited by:
yasar arafathHi Yasar,
please check the settings in the EH&S IMG for the RM-value assignment types:
Basic Data and Tools -> Specification Management -> Specification Database Structure -> Settings for Value Assignment -> Set Up Table-Based Value Assignment.
Are the classes and characteristics exists in the client?
-> check with transaction CL02, class type 100, class SAP_RMS*
Best regards,
Roland -
Batch determination in delivery proposes batch already scheduled
For one specific plant, when batch determination is done in the delivery, batches already scheduled for delivery are being proposed as still available. What can be causing this?
Hello,
I finally solved this issue, here are the steps I did to find the solution:
1. In transaction SPRO
->Logistics-General->Batch Management->Batch Determination and Batch Check->Strategy Types->Define Sales and Distribution Strategy Types
Check the condition Type (In my case SD01), the Field Class contains the selection class with the logic to determine stock (In my case Z_MM_FERT)
Chek the Sort Sequence (In my case SEQUENCIA)
2. Go to transaction CU72 with the Sort Sequence (SEQUENCIA), in characteristic must have the following values:
LOBM_VFDAT Expiration date, shelf life Ascending (Checked)
3. Go to transaction CL02 with the class founded in the previous step (Z_MM_FERT), in the characteristics TAB must have the following values:
LOBM_VFDAT Expiration date, shelf life
LOBM_ZUSTD Status of Batch
LOBM_QNDAT Next Insp. Date for Batch
LOBM_LVORM Deletion Ind. for Batches
4. Go to transaction MM03 with the material that you have in Delivery, chek the TAB Classification, Option Batch 022, the material must be associated to the selection Class (Z_MM_FERT), but it must be associated trought transaction MM01
5. In transaction OVZ9, double click in the row with the column Availability check = CH Batches and Checking Rule = B SD Delivery
Option Include Deliveries, must be Checked.
6. Material that you have in Delivery, must be created in transaction VCH1 with the according Strategy Type (SD01)
Best regards,
Alejandro Lopez -
Helllo Guru's,
Willl anyone give a clear example for variant configuration dependencies and how the dependency code works, it is hard time for me to understand by looking at SAP Library.
Full points to the answerHello PV,
Try the following simple dependencies.
Once you have setup the classification, class type 300 and created a configurable material in MM.
Assign the Material to the Configuration profile in transaction CU41.
Then create a BOM, with 2 variable parts.
So lets say you have two characteristic values possible in class type 300.
Characterisic_1 = 'A' or Part 1 in the BOM or Characteristic 1 = 'B' or Part 2 in the BOM. You must pre-define these before proceeding in transaction CT04 and assign to class type 300 - Class is created in transaction CL02.
To write a 'selection condition' dependency, please create it with the 'selection condition' following syntax using transaction CU01 - you can also create these dependencies locally in the BOM.
Characterisic_1 = 'A'. - Assign this syntax to Part 1
Characterisic_1 = 'B. - Assign this syntax to Part 2.
Try to configure the material using transaction CU50.
Hope this information helps?
Best Regards,
Ed -
MM - ML81N, Release Procedure for service entry sheet
Hi Gurus,
I would like to active the realease strategy for service.
in order to customize I set:
-Relase Groups
-Release Codes
-Release indicator
-Release startegues
Then I run ML81N TRX and I called a sheet to try. This sheet had to has done to one of the release strategy set...
on the menu (of this trx ML81N)Entry Sheet->Set Status->Release (is still turn off)
Where is the problem?, anybody could help me?
Tks in advance,
NachoHi,
please read the FAQ note 672719, question 5:
Setting up a release procedure is explained in the following short
example: All service entry sheets with material group 007 are supposed
to be subject to a release strategy. This release strategy requires that
the service entry sheets must be released with release code A1. Only the
cost center manager has the authorization for release code A1.
A) Create a characteristic for the material group:
o Call Transaction CT04. (Path in the SAP menu in R/3 Enterprise:
Cross-Application Components -> Classification System -> Master
Data -> Characteristics)
o Specify a name for the characteristic, for example CESSR_MATKL,
and choose the 'Create' pushbutton.
o On the 'Basic data' tab page, enter a description and keep the
'Released' status.
o On the 'Addnl data' tab page, enter table name CESSR and field
name MATKL (Material group).
o Enter class type 032 (Release strategy) on the 'Restrictions' tab
page and then save the characteristic.
Note: The release strategy must be based on a field of structure CESSR.
Using Transaction SE11, you can display which other fields are available
in addition to the material group (field MATKL).
B) Create a class to which you assign the characteristic:
o Call Transaction CL02. (Path in the SAP menu in R/3 Enterprise:
Cross-Application Components -> Classification System -> Master
Data -> Classes)
o Enter a class name, for example FRG_ESSR, and class type 032 (for
release strategy) and then choose the 'Create' pushbutton.
o On the 'Basic data' tab page, enter any name. (Keep the
'Released' status.)
o Enter characteristic CESSR_MATKL on the 'Char.' tab page and then
save the class.
C) Now carry out the required Customizing settings. Follow IMG path
(Transaction SPRO) 'Materials Management -> External Services Management
Seite 4
-> Define Release Procedures for Service Entry Sheet'
o At first, you must create a release group (for example 03). For
that, choose 'Release Groups', then choose 'New Entries', enter
'Rel. Group' = 03 and 'Class' = FRG_ESSR. Save the entry. The
system automatically determines value 3 (for entry of services
performed) for the release object.
o Now create release code A1 for release group 03. Choose 'New
Entries' and specify the following values: Grp = 03, Code = A1,
and description, for example cost center manager.
o Create two release indicators, for example A and B. Select the
'Released' field for release indicator B and save the entries.
(Note: A release strategy must at least contain two release
indicators. The first indicator (here A) must be defined as
locked, the last indicator as released. Furthermore, the general
changeability of the service entry sheet and the behavior for
value changes are defined via the release indicators.)
o Finally create the release strategy. Choose 'New Entries' and
specify the following values: Release group = 03, release
strategy, for example RS, release codes = A1. Assign the two
release indicators A and B via 'Release statuses'. Assign
material group 007 via 'Classification'. Save the release
strategy.
D) Assign the authorization for release code A1 and release group 03 to
the cost center manager. In role maintenance (Transaction PFCG), you can
for example use the default values for Transaction ML85 for that.
Regards,
Edit -
Create content modell, logical/physical document class, TA CT04/cl02/dc10
Dear experts,
Im about to get to know the SAP DMS. Content Server is already running working as well as the content repositories. I now wanna set up a content modell for testing with knowledge provider.
Im a bit confused about the different ways of doing that. What is actually the difference between creating a CHAR in TA ct04, creating a class in Cl02 with type 017 and the alternative of creating a content model with TA SRMCMCREATE or directly in the document modelling workbench.
Once ive hopefully understood the difference how can i start actually creating / uploading real (physical documents) cause in dont understand what TAs cvn01n/02n/03n are for.
There is a large number of function modules for kpro. Fo example when testing SDOK_LOIOS_CREATE i have to enter an RFC destination. What do i have to type in as RFC destination intending to store in content repositories of content server?
I know thats more than one question at a time but i would be very pleased some of these get answered.
Thanks a lot in advance.Dear Christian,
I would like to start providing you information with CT04 question. Here the CHAR value is used for maintaining the type of classification characteristics. The CHAR entry stands for 'Character' type which
means you can add alphabetical and numerical values to this classification characteristic. Transaction CT04 is normally used for creating classification characteristics. In CL02 you can create a class for
classification and then add the characteristics to it. In the standard class type 017 is used for classifying document info records.
Transaction CV01N/CV02N/CV03N are used in standard for document managment functionalities. Here you can create/edit/display your document info records. These document info records are like a frame for your original files which could be added to an info record and then checked into your Content Server.
During this check in function the KPRO function modules are used too.
For further information I would recommend you to see the SAP online documentation under http://help.sap.com.
Best regards,
Christoph -
Need all transaction codes related to SD and MM
hi
i am in need of need all transaction codes related to SD and MM.
can anyone help me to get it.
thanks in advance.Hi,
The most frequently used transaction codes are as follows:
1. VS00 - Master data
2. VC00 - Sales Support
3. VA00 - Sales
4. VL00 - Shipping
5. VT00 - Transportation
6. VF00 - Billing
Others as follows:
At Configuration:
1. VOV8 - Define Sales documents type (header)
2. OVAZ - Assigning Sales area to sales documents type
3. OVAU - Order reasons
4. VOV4 - Assign Item categoreies(Item cat determination)
5. VOV6 - Scedule line categories
6. OVAL - To assign blocks to relevant sales documents type
7. OVLK - Define delivery types
8. V/06 - Pricing
9. V/08 - Maintain pricing procedure
10.OVKP - Pricing proc determination
11.V/07 - Access sequence
Enduser:
1. Customer Master Creation-VD01 and XD01 (for full inclu company code)
VD02 - Change Customer
VD03 - Display Customer
VD04 - Customer Account Changes
VD06 - Flag for Deletion Customer
XD01 - Create Customer
XD02 - Modify Customer
XD03 - Display Customer
2. Create Other material -
MM00
3. VB11- To create material determination condition record
4. CO09- Material availability Overview
5. VL01 - Create outbound delivery with ref sales order
6. VL04 - Collective processing of delivery
7. VA11 - Create Inquiry
VA12 - Change Inquiry
VA13 - Display Inquiry
Sales & Distribution
Sales order / Quote / Sched Agreement / Contract
· VA01 - Create Order
· VA02 - Change Order
· VA03 - Display Order
· VA02 - Sales order change
· VA05 - List of sales orders
· VA32 - Scheduling agreement change
· VA42 - Contract change
· VA21 - Create Quotation
· VA22 - Change Quotation
· VA23 - Display Quotation
Billing
· VF02 - Change billing document
· VF11 - Cancel Billing document
· VF04 - Billing due list
· FBL5N - Display Customer invoices by line
· FBL1N - Display Vendor invoices by line
Delivery
· VL02N - Change delivery document
· VL04 - Delivery due list
· VKM5 - List of deliveries
· VL06G - List of outbound deliveries for goods issue
· VL06P - List of outbound deliveries for picking
· VL09 - Cancel goods issue
· VT02N - Change shipment
· VT70 - Output for shipments
General
· VKM3, VKM4 - List of sales documents
· VKM1 - List of blocked SD documents
· VD52 - Material Determination
MM Transaction Code
All transaction are stored in table TSTC.
Transaction for MM module start with M.
IH09 - Display Material
MM01 - Create Material
MM02 - Change Material
MM03 - Display Material
MM50 - List Extendable Materials
MMBE - Stock Overview
MMI1 - Create Operating Supplies
MMN1 - Create Non-Stock Material
MMS1 - Create Service
MMU1 - Create Non-Valuated Material
ME51N - Create Purchase Requisition
ME52N - Change Purchase Requisition
ME53N - Display Purchase Requisition
ME5A - Purchase Requisitions: List Display
ME5J - Purchase Requisitions for Project
ME5K - Requisitions by Account Assignment
MELB - Purch. Transactions by Tracking No.
ME56 - Assign Source to Purch. Requisition
ME57 - Assign and Process Requisitions
ME58 - Ordering: Assigned Requisitions
ME59 - Automatic Generation of POs
ME54 - Release Purchase Requisition
ME55 - Collective Release of Purchase Reqs.
ME5F - Release Reminder: Purch. Requisition
MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment
MBRL - Return Delivery per Mat. Document
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MB1B - Transfer Posting
MIBC - ABC Analysis for Cycle Counting
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI21 - Print physical inventory document
MI04 - Enter Inventory Count with Document
MI05 - Change Inventory Count
MI06 - Display Inventory Count
MI09 - Enter Inventory Count w/o Document
MI34 - Batch Input: Enter Count
MI35 - Batch Input: Post Zero Stock Balance
MI38 - Batch Input: Count and Differences
MI39 - Batch Input: Document and Count
MI40 - Batch Input: Doc., Count and Diff.
MI08 - Create List of Differences with Doc.
MI10 - Create List of Differences w/o Doc.
MI20 - Print List of Differences
MI11 - Physical Inventory Document Recount
MI07 - Process List of Differences
MI37 - Batch Input: Post Differences
CT01 - Create Characteristic
CT02 - Change Characteristic
CT03 - Display Characteristic
CL01 - Create Class
CL02 - Classes
CL03 - Display Class
CL04 - Delete Class
CL2B - Class Types
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Apr 7, 2008 12:53 PM -
Transport of Characteristics management - CT04 and CL02
Hello,
I wonder if you like to carry all environments and characteristics of the classes created by material transactions CT04 and CL02, perform all the settings in the environment of testing and must pass to the productive environment, it is possible to transport? Or have to repeat all the configuration in other environments?
Thanks.Hi
Maintainenace of Charcteristics and classes is not a configuration, it is a master data.
Some of the master data can be transported like tax codes.
But we cannot transport classes and Characteristics. You need to replicate all the relevant data in production.
If you have a lot of data then prepare data migration tolls like LSMW, BDC and BAPI's
Thanks & Regards
Kishore -
List of SAP Enjoy Transactions
Does any one has the list of SAP Enjoy transactions.
please send me [email protected]
It is required immediately. Pls Help.Hi
Tcode for MM Module
All transaction are stored in table TSTC.
Transaction for MM module start with M.
IH09 - Display Material
MM01 - Create Material
MM02 - Change Material
MM03 - Display Material
MM50 - List Extendable Materials
MMBE - Stock Overview
MMI1 - Create Operating Supplies
MMN1 - Create Non-Stock Material
MMS1 - Create Service
MMU1 - Create Non-Valuated Material
ME51N - Create Purchase Requisition
ME52N - Change Purchase Requisition
ME53N - Display Purchase Requisition
ME5A - Purchase Requisitions: List Display
ME5J - Purchase Requisitions for Project
ME5K - Requisitions by Account Assignment
MELB - Purch. Transactions by Tracking No.
ME56 - Assign Source to Purch. Requisition
ME57 - Assign and Process Requisitions
ME58 - Ordering: Assigned Requisitions
ME59 - Automatic Generation of POs
ME54 - Release Purchase Requisition
ME55 - Collective Release of Purchase Reqs.
ME5F - Release Reminder: Purch. Requisition
MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment
MBRL - Return Delivery per Mat. Document
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MB1B - Transfer Posting
MIBC - ABC Analysis for Cycle Counting
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI21 - Print physical inventory document
MI04 - Enter Inventory Count with Document
MI05 - Change Inventory Count
MI06 - Display Inventory Count
MI09 - Enter Inventory Count w/o Document
MI34 - Batch Input: Enter Count
MI35 - Batch Input: Post Zero Stock Balance
MI38 - Batch Input: Count and Differences
MI39 - Batch Input: Document and Count
MI40 - Batch Input: Doc., Count and Diff.
MI08 - Create List of Differences with Doc.
MI10 - Create List of Differences w/o Doc.
MI20 - Print List of Differences
MI11 - Physical Inventory Document Recount
MI07 - Process List of Differences
MI37 - Batch Input: Post Differences
CT01 - Create Characteristic
CT02 - Change Characteristic
CT03 - Display Characteristic
CL01 - Create Class
CL02 - Classes
CL03 - Display Class
CL04 - Delete Class
CL2B - Class Types
Important SAP MM Tcodes 1
ME01 Maintain Source List
ME03 Display Source List
ME04 Changes to Source List
ME05 Generate Source List
ME06 Analyze Source List
ME07 Reorganize Source List
ME08 Send Source List
ME0M Source List for Material
ME11 Create Purchasing Info Record
ME12 Change Purchasing Info Record
ME13 Display Purchasing Info Record
ME14 Changes to Purchasing Info Record
ME15 Flag Purch. Info Rec. for Deletion
ME16 Purchasing Info Recs. for Deletion
ME17 Archive Info Records
ME18 Send Purchasing Info Record
ME1A Archived Purchasing Info Records
ME1B Redetermine Info Record Price
ME1E Quotation Price History
ME1L Info Records Per Vendor
ME1M Info Records per Material
ME1P Purchase Order Price History
ME1W Info Records Per Material Group
ME1X Buyer's Negotiation Sheet for Vendor
ME1Y Buyer's Negotiat. Sheet for Material
ME21 Create Purchase Order
ME21N Create Purchase Order
ME22 Change Purchase Order
ME22N Change Purchase Order
ME23 Display Purchase Order
ME23N Display Purchase Order
ME24 Maintain Purchase Order Supplement
ME25 Create PO with Source Determination
ME26 Display PO Supplement (IR)
ME27 Create Stock Transport Order
ME28 Release Purchase Order
ME29N Release purchase order
ME2A Monitor Confirmations
ME2B POs by Requirement Tracking Number
ME2C Purchase Orders by Material Group
ME2J Purchase Orders for Project
ME2K Purch. Orders by Account Assignment
ME2L Purchase Orders by Vendor
ME2M Purchase Orders by Material
ME2N Purchase Orders by PO Number
ME2O SC Stock Monitoring (Vendor)
ME2S Services per Purchase Order
ME2V Goods Receipt Forecast
ME2W Purchase Orders for Supplying Plant
ME308 Send Contracts with Conditions
ME31 Create Outline Agreement
ME31K Create Contract
ME31L Create Scheduling Agreement
ME32 Change Outline Agreement
ME32K Change Contract
ME32L Change Scheduling Agreement
ME33 Display Outline Agreement
ME33K Display Contract
ME33L Display Scheduling Agreement
ME34 Maintain Outl. Agreement Supplement
ME34K Maintain Contract Supplement
ME34L Maintain Sched. Agreement Supplement
ME35 Release Outline Agreement
ME35K Release Contract
ME35L Release Scheduling Agreement
ME36 Display Agreement Supplement (IR)
ME37 Create Transport Scheduling Agmt.
ME38 Maintain Sched. Agreement Schedule
ME39 Display Sched. Agmt. Schedule (TEST)
ME3A Transm. Release Documentation Record
ME3B Outl. Agreements per Requirement No.
ME3C Outline Agreements by Material Group
ME3J Outline Agreements per Project
ME3K Outl. Agreements by Acct. Assignment
ME3L Outline Agreements per Vendor
ME3M Outline Agreements by Material
ME3N Outline Agreements by Agreement No.
ME3P Recalculate Contract Price
ME3R Recalculate Sched. Agreement Price
ME3S Service List for Contract
ME41 Create Request For Quotation
ME42 Change Request For Quotation
ME43 Display Request For Quotation
ME44 Maintain RFQ Supplement
ME45 Release RFQ
ME47 Create Quotation
ME48 Display Quotation
ME49 Price Comparison List
ME4B RFQs by Requirement Tracking Number
ME4C RFQs by Material Group
ME4L RFQs by Vendor
ME4M RFQs by Material
ME4N RFQs by RFQ Number
ME4S RFQs by Collective Number
ME51 Create Purchase Requisition
ME51N Create Purchase Requisition
ME52 Change Purchase Requisition
ME52N Change Purchase Requisition
ME52NB Buyer Approval: Purchase Requisition
ME53 Display Purchase Requisition
ME53N Display Purchase Requisition
ME54 Release Purchase Requisition
ME54N Release Purchase Requisition
ME55 Collective Release of Purchase Reqs.
ME56 Assign Source to Purch. Requisition
ME57 Assign and Process Requisitions
ME58 Ordering: Assigned Requisitions
ME59 Automatic Generation of POs
ME59N Automatic generation of POs
ME5A Purchase Requisitions: List Display
ME5F Release Reminder: Purch. Requisition
ME5J Purchase Requisitions for Project
ME5K Requisitions by Account Assignment
ME5R Archived Purchase Requisitions
ME5W Resubmission of Purch. Requisitions
ME61 Maintain Vendor Evaluation
ME62 Display Vendor Evaluation
ME63 Evaluation of Automatic Subcriteria
ME64 Evaluation Comparison
ME65 Evaluation Lists
ME6A Changes to Vendor Evaluation
ME6B Display Vendor Evaln. for Material
ME6C Vendors Without Evaluation
ME6D Vendors Not Evaluated Since...
ME6E Evaluation Records Without Weighting
ME6F Print
ME6G Vendor Evaluation in the Background
ME6H Standard Analysis: Vendor Evaluation
ME6Z Transport Vendor Evaluation Tables
ME80 Purchasing Reporting
ME80A Purchasing Reporting: RFQs
ME80AN General Analyses (A)
ME80F Purchasing Reporting: POs
ME80FN General Analyses (F)
ME80R Purchasing Reporting: Outline Agmts.
ME80RN General Analyses (L,K)
ME81 Analysis of Order Values
ME81N Analysis of Order Values
ME82 Archived Purchasing Documents
ME84 Generation of Sched. Agmt. Releases
ME84A Individual Display of SA Release
ME85 Renumber Schedule Lines
ME86 Aggregate Schedule Lines
ME87 Aggregate PO History
ME88 Set Agr. ***. Qty./Reconcil. Date
ME91 Purchasing Docs.: Urging/Reminding
ME91A Urge Submission of Quotations
ME91E Sch. Agmt. Schedules: Urging/Remind.
ME91F Purchase Orders: Urging/Reminders
ME92 Monitor Order Acknowledgment
ME92F Monitor Order Acknowledgment
ME92K Monitor Order Acknowledgment
ME92L Monitor Order Acknowledgment
ME97 Archive Purchase Requisitions
ME98 Archive Purchasing Documents
ME99 Messages from Purchase Orders
ME9A Message Output: RFQs
ME9E Message Output: Sch. Agmt. Schedules
ME9F Message Output: Purchase Orders
ME9K Message Output: Contracts
ME9L Message Output: Sched. Agreements
MEAN Delivery Addresses
MEB0 Reversal of Settlement Runs
MEB1 Create Reb. Arrangs. (Subseq. Sett.)
MEB2 Change Reb. Arrangs. (Subseq. Sett.)
MEB3 Displ. Reb. Arrangs. (Subseq. Sett.)
MEB4 Settlement re Vendor Rebate Arrs.
MEB5 List of Vendor Rebate Arrangements
MEB6 Busn. Vol. Data, Vendor Rebate Arrs.
MEB7 Extend Vendor Rebate Arrangements
MEB8 Det. Statement, Vendor Rebate Arrs.
MEB9 Stat. Statement, Vendor Rebate Arrs.
MEBA Comp. Suppl. BV, Vendor Rebate Arr.
MEBB Check Open Docs., Vendor Reb. Arrs.
MEBC Check Customizing: Subsequent Sett.
MEBE Workflow Sett. re Vendor Reb. Arrs.
MEBF Updating of External Busn. Volumes
MEBG Chg. Curr. (Euro), Vend. Reb. Arrs.
MEBH Generate Work Items (Man. Extension)
MEBI Message, Subs.Settlem. - Settlem.Run
MEBJ Recompile Income, Vendor Reb. Arrs.
MEBK Message., Subs. Settlem.- Arrangment
MEBM List of settlement runs for arrngmts
MEBR Archive Rebate Arrangements
MEBS Stmnt. Sett. Docs., Vend. Reb. Arrs.
MEBT Test Data: External Business Volumes
MEBV Extend Rebate Arrangements (Dialog)
MECCP_ME2K For Requisition Account Assignment
MEDL Price Change: Contract
MEI1 Automatic Purchasing Document Change
MEI2 Automatic Document Change
MEI3 Recompilation of Document Index
MEI4 Compile Worklist for Document Index
MEI5 Delete Worklist for Document Index
MEI6 Delete purchasing document index
MEI7 Change sales prices in purch. orders
MEI8 Recomp. doc. index settlement req.
MEI9 Recomp. doc. index vendor bill. doc.
MEIA New Structure Doc.Ind. Cust. Sett.
MEIS Data Selection: Arrivals
MEK1 Create Conditions (Purchasing)
MEK2 Change Conditions (Purchasing)
MEK3 Display Conditions (Purchasing)
MEK31 Condition Maintenance: Change
MEK32 Condition Maintenance: Change
MEK33 Condition Maintenance: Change
MEK4 Create Conditions (Purchasing)
MEKA Conditions: General Overview
MEKB Conditions by Contract
MEKC Conditions by Info Record
MEKD Conditions for Material Group
MEKE Conditions for Vendor
MEKF Conditions for Material Type
MEKG Conditions for Condition Group
MEKH Market Price
MEKI Conditions for Incoterms
MEKJ Conditions for Invoicing Party
MEKK Conditions for Vendor Sub-Range
MEKL Price Change: Scheduling Agreements
MEKLE Currency Change: Sched. Agreements
MEKP Price Change: Info Records
MEKPE Currency Change: Info Records
MEKR Price Change: Contracts
MEKRE Currency Change: Contracts
MEKX Transport Condition Types Purchasing
MEKY Trnsp. Calc. Schema: Mkt. Pr. (Pur.)
MEKZ Trnsp. Calculation Schemas (Purch.)
MELB Purch. Transactions by Tracking No.
MEMASSIN Mass-Changing of Purch. Info Records
MEMASSPO Mass Change of Purchase Orders
MEMASSRQ Mass-Changing of Purch. Requisitions
MENU_MIGRATION Menu Migration into New Hierarchy
MEPA Order Price Simulation/Price Info
MEPB Price Info/Vendor Negotiations
MEPO Purchase Order
MEQ1 Maintain Quota Arrangement
MEQ3 Display Quota Arrangement
MEQ4 Changes to Quota Arrangement
MEQ6 Analyze Quota Arrangement
MEQ7 Reorganize Quota Arrangement
MEQ8 Monitor Quota Arrangements
MEQB Revise Quota Arrangement
MEQM Quota Arrangement for Material
MER4 Settlement re Customer Rebate Arrs.
MER5 List of Customer Rebate Arrangements
MER6 Busn. Vols., Cust. Reb. Arrangements
MER7 Extension of Cust. Reb. Arrangements
MER8 Det. Statement: Cust. Rebate Arrs.
MER9 Statement: Customer Reb. Arr. Stats.
MERA Comp. Suppl. BV, Cust. Rebate Arrs.
MERB Check re Open Docs. Cust. Reb. Arr.
MERE Workflow: Sett. Cust. Rebate Arrs.
MEREP_EX_REPLIC SAP Mobile: Execute Replicator
MEREP_GROUP SAP Mobile: Mobile Group
MEREP_LOG SAP Mobile: Activity Log
MEREP_MIG SAP Mobile: Migration
MEREP_MON SAP Mobile: Mobile Monitor
MEREP_PD SAP Mobile: Profile Dialog
MEREP_PURGE SAP Mobile: Purge Tool
MEREP_SBUILDER SAP Mobile: SyncBO Builder
MEREP_SCENGEN SAP Mobile: SyncBO Generator
MERF Updating of External Busn. Volumes
MERG Change Curr. (Euro) Cust. Reb. Arrs.
MERH Generate Work Items (Man. Extension)
MERJ Recomp. of Income, Cust. Reb. Arrs.
MERS Stmnt. Sett. Docs. Cust. Reb. Arrs.
MEU0 Assign User to User Group
MEU2 Perform Busn. Volume Comp.: Rebate
MEU3 Display Busn. Volume Comp.: Rebate
MEU4 Display Busn. Volume Comp.: Rebate
MEU5 Display Busn. Volume Comp.: Rebate
MEW0 Procurement Transaction
MEW1 Create Requirement Request
MEW10 Service Entry in Web
MEW2 Status Display: Requirement Requests
MEW3 Collective Release of Purchase Reqs.
MEW5 Collective Release of Purchase Order
MEW6 Assign Purchase Orders WEB
MEW7 Release of Service Entry Sheets
MEW8 Release of Service Entry Sheet
MEW9 mew9
MEWP Web based PO
MEWS Service Entry (Component)
ME_SWP_ALERT Display MRP Alerts (Web)
ME_SWP_CO Display Purchasing Pricing (Web)
ME_SWP_IV Display Settlement Status (Web)
ME_SWP_PDI Display Purchase Document Info (Web)
ME_SWP_PH Display Purchasing History (Web)
ME_SWP_SRI Display Schedule Releases (Web)
ME_WIZARD ME: Registration and Generation
<b>Please Awards Point if help full</b>Thanks
Pankaj Kumar -
Transport Classes (CL02) and Assignments (CL24N)
Hi,
Is there any way to transport/export classes (CL02) and Assign Objects/Classes to class (CL24N) to other system?
We have done the workflow mapping in these transactions. So we need to transport this data to Quality and Production systems. Actually this is a master data (Master data can't be transported). Is there any other way?
Thanks in advance.
Thanks & Regards,
Govind.Hi Govind !
Do you have faced that when delete a Release strategy from transaction OMGQ , it is not deleted from the assignment of Object (rel.strt) to Class(032) ?
When I try to delete it manually the system display the message ...
Object not found
Message no. CL 504
Diagnosis
You have entered an object which has not been created.
Procedure
Either create the object, or use another object.
I would appreciate any tip to delete this assignment.
Thanks in advance!
Carlos Hurtado
Maybe you are looking for
-
Where can i download an oracle XE 10 win32 edition?
I have to migrate some sqlserver databases, in an old win2003 machine, to oracle11/linux. I've found a method, in oracle docs, implemented with sqldeveloper, jdts jdbc and a local oracle repository. I think the only choice here is Oracle XE 10, since
-
Records Management, Framework background call
Hi all. Here some problems. First of all - the target: Create additional checks and change Circular (disposition) in background mode. As a sample implementation Ive selected the CL_SRM_DIS_VISUAL->START_DISPOSITION_EXT method. But in this method di
-
What's the dialog box when you launch Aperture for the first time?
I bought Aperture 3 from the App Store, installed it, and when I launched it something odd happened: I was interacting with another application, and when Aperture started up it out up the main window and a dialog box popped up that asked "Would you l
-
Can some columns be exculded from hide feature of panelCollection?
Hi All, First of all KUDOS to OTN forum developers/users for the new AVATAR of forums. [clap...clap!!] I am using panelCollection for hiding and showing columns in my table. Now there exists a primary key column in my table. What I want to do is, use
-
Uninstalling iPhoto Update from iLife
Does anyone know how to uninstall the iPhoto update from iLife (and even for iMovie too)? I really don't like the new iPhoto as simple things are now more difficult or aren't available anymore. The changes seem more superficial as I haven't found any