Batch Determination in SD - Need for Material Master Classification View

Hi!
Is it mandatory to have the classification view of the material maintained to enable expiry date based batch determination at delivery creation?
I have configured BD for the delivery. When testing with a material for which the classification view is maintained, the batch is determined. When testing with a material for which the classification view is not maintained, the batch is not determined.
Appreciate that this may seem like a strange question given what the testing shows but I am working with a colleague who is adamant that the classification view on the material master is not required.
Any casting votes would be much appreciated and rewarded accordingly. Thanks, Duncan

Classification of batches is mandatory if you want to use the batch determination feature.
source: http://help.sap.com/saphelp_erp2005/helpdata/en/4d/2b8bd043ad11d189410000e829fbbd/frameset.htm

Similar Messages

Could sap do mass craete/update for material master classification?

Hi Expert,
Now we craeted new classifcaiton for material master. It need be assigned to related many parts. May I query Could sap do mass craete/update for material master classification? How to do this ?
Thanks
Alice

Hi,
Another option is using LSMW, please refer to below thread for more details:
Classification view in MM01 with LSMW
cheers,

Material Master Classification view

Hi all,
I have some doubt in Material Master Classification view.
I want to know the Database Table name in which the field Class Number
is stored.
I know that these tables are stored in the stucture ( RMCLF
) during creation of material master.
Thanks in advance

KLART is for Class Type & not for Class number ...
also i need the table where i can see it ...
Thanks in advance

Material Master - classification view - URGENT

I am coding a proxy for Material master creation. I have done for all the views except for Classification view. Can any one tell me how to start coding for this view.
Thanks,
-Naveen.

Try function module CLFM_OBJECT_CLASSIFICATION. You cannot do a BDC for it. You can also try standard programs RCCLBI03, RCCLBI02 or RCCLBI03 but they may not be relevant in your case.

Multiple class types for material master classification display default.

Hello,
We are running on R/3 4.7. We use several different class types for our material masters (001 and Z01). The problem this creates is the end user having to constantly tell the system which class type to use when going to the classification screen for different materials with different class types. If a user views one material's classification page with a particular class type (001) then looks at another material with a different class type (Z01) the system tries to pull in information from the last materials class type (001). The system tells the user there are no assignments for the class (001) in the material their viewing but there is one for class type (Z01). The user then has to select the class type that applies to the material master their trying to view. Is there a way for the system to automatically see when a material has only one class type assigned to it for it to automatically default it in without the user having to specify the class type?
Thanks,
JRW

Hi,
Check the configuration, have you maintained default class type for material type.
Logistic General> Material Master> Basic Setting> Material Type> Define attributes of Material Types>Select the material type> Double click on material type--> Class type
Edited by: P. Dhamane on Jun 4, 2010 3:21 PM

Table for Material master sales view

Hi SAP Gurus,
I have a list of materials (around 2000), now I want to check for how many material the sales view is not maintained. So, is there any table to find out my requirement.
Thanks
Sha

check below tables
MVKE Sales Org, distribution channel
MLAN Sales data, tax indicator, tax

Material master classification view mandatory

Hi All,
Can we make classification view required for any material creation using MM01.
We want the user to maintain a value in the classification view before the user is allowed to save and create a new material.
Any help would be greatly appreciated

Hi SAP friends,
I found a solution to this problem.
Use the user exit EXIT_SAPLMGMU_001. Call the function module MAIN_PARAMETER_GET to get the PSTAT (maintenance status) during material master creation. If PSTAT does not have a 'C' value, then it means the classification view was not maintained.
To check further if a class type and a class was maintained in the view itself, call the function module CLAP_DDB_ALLOCATION_FR_BUFFER. Pass the value 'MARA' to the PTABLE parameter and the corresponding CLASSTYPE (could be '022', as is my case) and the I_CLASS ('FIFO_BATCH' in my case). This function module will return the T_ALLOCATIONS table. If the table is blank, it means no class type and class were maintained.
Then you can just display the appropriate error message.
Hope this helps.
Aileen

LSMW for material master using Batch input recording method

Dears,
I am using Batch input recording method to upload material master data. But while selecting views , I need to scroll to select the vies lets say Plant storage loc view. While scrolling and selecting ,views are not recorded propelry . That is when I run in foreground system selects only basic data and purchasing views but the plant data views are not selected(palnt data views are selected by scrolling while recording).
How to resolve this issue.
Pls help
Regards
Kamesh

HI,
, I need to scroll to select the vies lets say Plant storage loc view. While scrolling and selecting ,views are not recorded propelry
Don,t scroll use Page down button from key Bord
like select Basis view and then press page down button from key board ,then you will get next view now select it
Regards
Kailas Ugale

Need to create a Store Business document type for material master and store a sharepoint link

Hello,
I need to create a Store business document type for material master and store a URL link . How do I do that?( or is there any functionality to upload a document for a store business document that it will automatically saves to sharepoint?)
Thanks,
Ran.

>
dhayes12 wrote:
> A) When I do the (Material Backflush) MFBF for the 04 type, the Inspection Lot gets created OK. I then can go into QA32 and assign the correct Inspection Plat by clicking the Inspection Lot button.
>
> B) When I do the MIGO via the Purchase Order (type Z01), it will not create the Lot if I have the Multiple Specs selected in the QM Material Master MM02. If, I turn off the Multiple Specs in the QM Material Master and create a new PO and MIGO, it will create the Lot, however, it automatically assigns the lot to the wrong Inspection Plan (2nd Plan see above) I need to be able to select the plan like I can with the 04 type.
>
> Is their some setting that can be changed in Config or somewhere that acts the same way as example A above?
For case A, create insp plan with usage "1- production" If you have one IP with this usage for given material then system will assign Plan to lot automatically. In your case for second plan update usage as 1.
For case B, system should assign 1st plan make sure for both plan udage is correct. for 1st plan usage should be 5 while 2nd plan usage should be 1. Now if your 1st have status 4 and key date before lot date then system will assign plan auto.
Thanks!!!

Most use ful t code for Material Master changing

Dear All,
Can any one give me most useful T-codes for create, change and display material master.
I have one T-code which is very useful for material master it is "MM50". With help of this tcode you can see material extend detail and also you can delete mass material with help of this tcode.
So please use it and also give me other this type of tcodes.
Regards,
Mahesh Wagh

Hi,
MM17, LSMW, MM50 --- These are the 3 main transactions which is used frequently to Mass change the Material master.
There is one more option is there using BDC Upload.
Batch Data Communication or BDC is a batch interfacing technique that SAP developed. It is mainly used for uploading data into the SAP R/3 system. BDC works by simulating the user input from transactional screen via an ABAP program.
The data input data file will come in the form of a flat file which the user save as file type txt file or prn file from the Microsoft Excel program. An Abaper will create a program to read the text file and upload into the SAP system.
Transaction -- SHDB will be used to record the change material master. After, the simulation, the Abaper can generate a sample program and modify from there. It makes the programming easier and faster.
For a BDC upload you need to write a program which created BDC sessions.
hope you got it. Take a help of ABAPer for this BDC Upload.
rgds
Chidanand

Step by step instruction for Using LSMW Recoding method for Material Master

Guys,
Can some one explain step by step procedure for uploading the materials master data to R/3 by using LSMW Recoding method. By the time you reply I will go through the rule of uploading the data..
Thanks guys,
Dhanu.

Hi,
The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.
The LSM Workbench covers the following steps:
(1)Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files)
(2)Convert the data from source format to target format
(3)Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).
The Steps for LSME are:
Example: Customer Master upload:
LSMW to Update Customer Master Records with Transaction Recording
Call Legacy System Migration Workbench by entering transaction code LSMW. Every conversion task is grouped together as Project / Subproject / Object structure. Create a Project called LSMW_DEMO and a Subproject as CUSTOMERS and Object as CUST_REC
Step 1: Maintain Object attributes
In this example, you will be updating the customer master records with the help of recording a transaction (XD02). Choose radio button Batch Input Recording and click on the recording overview icon to record the R/3 transaction. Enter the Recording name as XD02_REC, the description as Customer Master Updates Recording, and the transaction code as XD02.
Step 2. Maintain Source Structures
Give a name and a description to the source structure
Step 3. Maintain Source Fields
In this step, you need to list what fields are present in the source structure. The easiest way is to click on u2018Table Maintenanceu2019 icon to enter Fieldname, Type and Length for each field
Step 4: Maintain Structure Relations
Execute a step to u2018Maintain Structure Relationsu2019. Since, there is only one Source and Target Structure, the relationship is defaulted automatically.
Step 5: Maintain field mapping and conversion rules
Field RF02D-D0310 represents that you chose u2018Sales viewu2019 for the customer Master screen accordingly its value should be set to X. Keep your cursor on field RF02D-D0310 and click on Constant rule icon to choose the constant value of u2018Xu2019.
If your source file already has the field value, you choose rule u2018Source Fieldu2019.
Keep cursor on field u2018KUNNRu2019 and click on u2018Assign Source fieldu2019 icon to choose source field CUSTOMER from structure XD02S
Step 6: Maintain fixed values, translations, user-defined routines
You can also maintain re-usable translations and user-defined routines, which can be used across conversion tasks. In this case, that step is not required.
Step 7: Specify files
In this step, we define how the layout of the input file is. The input file is a [Tab] delimited with the first row as field names. It is present on my PC (local drive) as C:\XD02.txt.
Step 8: Assign files
Execute step u2018Assign Filesu2019 and the system automatically defaults the filename to the source structure.
Step 9: Read data
In this step, LSMW reads the data from the source file (from your PCu2019s local drive). You have the option to read only selected rows and convert data values to Internal format.
Step 10: Display read data
This step is optional. If required, you can review the field contents for the rows of data read.
Step 11: Convert data
This is the step that actually converts the source data (in source format) to a target format. Based on the conversion rules defined, source fields are mapped to target fields.
Step 12: Display Converted data
Again this is an optional step to view how the source data is converted to internal SAP format
Step 13: Create batch input session
Once the source data is converted in an internal format, you can create a batch session to process updates.
Step 14: Run Batch Input Session
You can execute the BDC session by Run Batch input session. Executing a batch input session is a standard SM35 transaction for managing BDC sessions. Once you have successfully executed the batch input session, the customer master records are updated in the system. You can confirm this by viewing the customer master records (XD03).
Follow the link for material master
http://www.sap123.com/showthread.php?t=98
Regards,
Biju K

Issue in LSMW for material master using standard input program RMDATIND!!

Hello guys,
I have a issue in LSMW for material master.
I have a custom field in MARA table. which I want to add in my LSMW.
I added the field in BMMH1 structure. I'm passing the value to this field, But it is not populated in the table when I run it.
Is there anything else I need to do apart from addition of field in the structure BMMH1.
Thanks in advance for your help.
Regards,
Sumeet....

see oss note 44410, it gives you a step by step overview.
https://service.sap.com/sap/support/notes/44410

BAPI for Material master update

Hello,
I need to upload and change data to the classification screen of Material master (MM01/02). I am thinking of using BAPI_CHARACT_CREATE and BAPI_CHARACT_CHANGE. Can we use BAPI_MATERIAL_SAVEDATA to upload and change characteristic data for material master(MM01/02)?
Can anybody provide me some sample code for mass upload and mass change of characteristic data to material master?
Thanks in advance
Rajesh.

Hi Rajesh,
You can use standard SAP program RCCLBI03 to do mass upload.
Please check the program documentation for more information.
Also you can take a look this BAPI/FM.
BAPI_OBJCL_CREATE
BAPI_OBJCL_CHANGE
CLVF_INSERT_AUSP
CLVF_UPDATE_AUSP
CLVF_VB_INSERT_CLASSIFICATION
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

SRM and MDM for material master in SRM contracts for multiple R/3

Dear all,
my question is:
We are implementing SRM 4.0 in classic scenario with multiple R/3 back-end and we want to set-up Global Outline Agreements in SRM in a multi-backend environment where the Material Master are not harmonized.
We heard that MDM and COntent Integraton can be a solution.
Then detailled question is:
Can we have 2 material numbers (e.g. ABC and XYZ) in 2 different R/3 systems refering the same product.
Have the mapping done in MDM (Content Integrator?) to a third material number:123
Replicating the material master 123 to SRM from MDM(?)
Create global Outline Agreements in SRM for Material Master 123.
Distribute the GOA as Outline Agreement to R/3 system 1 with the translation to ABC and to R/3 system 2 with the translation XYZ, all of that during the distribution step (or another).
Have the call-offs quantities correct on 123 in SRM and BW?
IF yes, how is it working, do you have some documentation discribing the scenario and the config steps to do?
Thanks in avance

Hello RD,
That's a good question.
You are on the right way. MDM is the tool for you.
But..
Content Integrator (CI) was first developped for Shell, to address the need of cross-referencing of material/supplier/category IDs, for:
- reporting purpose (actual Spend Analysis)
- mapping purpose (send of XML PO)
CI was later "fusionned" into the new MDM (1.0) solution.
So now, you can not order CI without MDM (even if some SRM slides still present CI).
But mapping API where developped for all inboud/outbound interfaces in SRM, for materials only (good luck for you).
You will find everywhere this piece of code:
Call ECI
    CALL FUNCTION 'BBP_PRODUCT_MAP'
      TABLES
        it_input          = lt_mapping_in
        et_output         = lt_mapping_out
      EXCEPTIONS
        logsys_not_found = 1
        driver_not_found = 2
        product_not_found = 3
        internal_error    = 4
        OTHERS            = 5.
So it is ok, you have the mapping call, but I don't know if all the rest of the process was really "finalized" (call of API mapping in CI, via XI). I personnaly never used it, but I assume it should work.
I my opinion your process is supported by SAP:
- Extract materials from both R/3 and consolidate them as a single product in MDM.
- Distribute this product into SRM.
- Maintain contracts on those products.
- Distribute them to R/3 (The ECI call is also used during contract distribution).
- Call offs corrects in SRM and BW
For MDM documentation, look at netweaver area of service.sap.com.
For MDM/SRM integration, look at SRM 4.0 spend analysis:
https://websmp206.sap-ag.de/~sapdownload/011000358700004424262004E/GlobalSpendOverview.ppt
For SRM contract distribution, call-offs, BW, look at SRM in details in service.sap.com/srm/SRM4.0:
https://websmp206.sap-ag.de/~sapdownload/011000358700001966382004E/contracten.ppt
For SRM5.0, see online help on help.sap.com.
Rgds
Christophe

Problem with mass IDoc for Material Master

Hi All,
Can anyone suggest a solution to work with mass IDocs for Material master?
We have DEBMDM and CREMDM as mass capable IDocs for Customer and Vendor. How do we get mass Material Master IDocs from R/3 in a single XML file?
Also the standard Material repository supplied with SAP MDM 5.5 SP3 doesn't have any XSD definition for MATMDM. Can anyone throw some light on this problem?
Regards
Pooja

Hello Pooja:
The standard way to do it is to generate a single file containing multiple idocs (And for the sake of performance, I suggest you stick to this technique).
In the case of material master, everything is straight forward. In the case of customer and vendor master, when data flows from R/3 to MDM no idoc conversion needs to be performed by XI.
However, for the case of customer and vendor master, when data flows from MDM to R/3, XI needs to separate the data in CREMDM to CREMAS and ADRMAS in order for R/3 to be able to process the idocs; as well as separate the data in DEBMDM to DEBMAS and ADRMAS.
The good thing is that you do not need to worry about all this mappings and conversions in XI. The only thing you need to do in XI is to import the standard business content for SAP MDM 5.5 into XI.
Hope this helps.
Regards,
Jorge.

Batch Determination in SD - Need for Material Master Classification View

Similar Messages

Maybe you are looking for