SAP R/3 форум ABAP консультантов
Russian ABAP Developer's Club

Home - FAQ - Search - Memberlist - Usergroups - Profile - Log in to check your private messages - Register - Log in - English
Blogs - Weblogs News

How to add new fields to material master view



 
Post new topic   Reply to topic    Russian ABAP Developer's Club Forum Index -> ММ
View previous topic :: View next topic  
Author Message
admin
Администратор
Администратор



Joined: 01 Sep 2007
Posts: 1640

PostPosted: Thu Oct 04, 2007 9:09 pm    Post subject: How to add new fields to material master view Reply with quote

Noddy guide to add new data fields to Material Master.
Author: jzeeman
Source: http: //www.sapfans.com/forums/viewtopic.php?t=43762

This guide should be used in conjunction with OSS note 44410 and IMG notes Logistics->Logistics Material Master->Material->Configure Customised Material Master.

Online Maintenance.

1. Add fields to append structure ZAEMARA.
Use data dictionary maintenance – SE11.

2. Generate table MARA.

3. Add fields to view MARU and generate.
Use data dictionary maintenance – SE11.

4. Create new sub-screen or add new fields to screen SAPLYMM1 9001.
Use Screen Painter – SE51.
Change flow logic to add fields to field: statement and to add any validation required. Generate screen.
If this is the first time additional data has been added to material master it will be necessary to create a new function group and associated programs. See Configure Customised Material Master paragraph Requirements.

5. If new sub-screen, add to Customer main screen.
Transaction OMT3.
Double click on ‘Std industry sequence’.
Choose customer screen and Details.
Change the first occurrence of 0001 (blank screen) to new screen number.
Save.
Back arrow.
Click on Transport button and choose required transport.

6. Add new MARA fields to table T130F. (in each client)
Use Transaction SM31. (make a copy of another ZZ field by typing over existing name).
Add to transport manually:- R3TR TABU T130F + individual keys.

7. Test Material create, change, display.

Batch data take-on.

1. Add new fields to structure CI_MMH1 and activate.
2. Activate BMMH1?.
3. Run RMDATING – Both options.
4. Change program YMM1001A to output new fields to BMMH1 from spreadsheet.


Live procedure to update material master with new fields.

1. Create spreadsheet of new data containing material number followed by data for each new field.

2. Save spreadsheet as tab delimited text file. Suggested name c:\temp\matrix.

3. Run program YMM1001A to read file output in 2 and create file for input to Sap standard material update program (RMDATIND).
The output filename must be the same as that expected by RMDATIND.
To check this use SM30 -> V_FILENAME -> Display -> Choose MATERIAL_MASTER_BTCI -> check value of Physical file. This can be changed if necessary using Maintenance mode.
You can check that the output from YMM1001A is in the correct format by running RMDATSHO. This is a display program which reads the same input as RMDATIND and displays it in a readable format.

4. Run RMDATING: This program generates code and only needs to be run once regardless of how many times the dataload is run.

5. Run RMDATIND: Sap standard material batch update. Can be run in check mode first by checking box – Check data, but do not update.

(Check value of running with BMV0? instead of online).
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Russian ABAP Developer's Club Forum Index -> ММ All times are GMT + 4 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum


All product names are trademarks of their respective companies. SAPNET.RU websites are in no way affiliated with SAP AG.
SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver and any other are registered trademarks of SAP AG.
Every effort is made to ensure content integrity. Use information on this site at your own risk.