Trx MM01.

Hi,
how can I set in MM01 trx in field Industry sector the default value
Mechanical engineering?
Best regards

Dear Friend,
In the T code MM01 key in Industry sector as Mechanical Engg.,select material type then press enter (for internal assignment assignment).Now select views screen pops up ,here u can select the views and click on save "Default Values" radio button.
Next time u enter MM01 T code the Industry and mat. type comes as default in the screen.
Thanks and Regards,
Uzair Hussain
<<<<Reward if helpful >>>>>

Similar Messages

Protecting long text in MM01 MM02

Hi all
my requirements is to protect material basic data long text (trx MM01, MM02) for a specific user. How can I do that?
Note that I can't use authority object M_MATE_MAN, cause only long text need to be protected.
My SAP release is 4.6C
Regards

Hi Stefano,
We had a similar requirement and we used the userexit to do prevent the changes. You can create a dummy auth and then if the field changes you can check this object to allow or disallow the changes.
EXIT_SAPLMGMU_001
Hope this helps
Deep

Error in adding custom fields to mm01/mm02/mm03 trx

Hello People,
To add my custom fields in the basic view tab of MM01 transaction, i have performed the following steps:-
1. Inserted the append structure in MARA table with the required fields.
2. Copied function group 'MGD1' to 'ZMGD1' and then set the layout of screen '0001' as per my requirement.
3. Then i made changes in spro as
SPRO->Logistics-General->Material Master->Configuring the material master->define structure of data screens for each screen sequence and inserted my program name( of function group 'ZMGD1') and screen number(0001) in 21(Std ind.(short) tab pages)->7(Basic Data 1)->8(sequence).
Now, if i click on SPRO option (view data screen), then i can see my fields added in basic data view...
but when i execute 'MM01/MM02/MM03' trx there my added fields do not appear....
Does anyone know where i am missing out??
Please suggest...
Thanks in advance..
Rgds,
Abhi

Here are some notes I have from when I recently added a new screen/subscreen to Material Master transactions. Hopefully this information will help you.
This guide should be used in conjunction with OSS note 44410 and IMG notes Logistics->Logistics Material Master->Material->Configure Customized Material Master.
Online Maintenance.
1. Add fields to append structure ZAEMARA.
Use data dictionary maintenance u2013 SE11
2. Generate table MARA.
3. Add fields to view MARU and generate.
Use data dictionary maintenance u2013 SE11.
4. Create new sub-screen or add new fields to screen SAPLYMM1 9001.
Use Screen Painter u2013 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 u2018Std industry sequenceu2019.
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. To include in 'Copy with Reference' processing - MM01, 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.

SCREEN EXIT MM01

Does anyone know the screen exit for disabling MARC fields in transaction code MM01...
fIELDS TO BE DISABLED:
- ABCIN
- CCFIX
tHANKS IN ADVANCE

Hi,
Try with
Logistics - General -> Material Master -> Field Selection -> Maintain Field Selection for Data Screens
In this config screen, u can hide fields transaction code wise. Like i tried for MARA-MEINS in trx MM02, and check hide radio button and it works. You can try the same for MARC table fields.
Sumit

Unable To Capture View in MM01

Dear All,
I am unable to capture the 'Accounting' view in MM01.
In recording in SHDB, I find the accounting view cannot be captured.
Please advice.
Regards,
Prosenjit.

Hi Prosenjit,
try to do this it may be help full to you...
while selecting the views in MM01 at the time of recording. If you want to capture Accounting view after selecting required views please press PAGE DOWN button in the key board then select Account view by doing this you can capture the Account view.....
please reward if this helpfull.

PLz Help me its urgent, how to add new field in mm01 basic data screen

Hi everyone,
plz tell me how to add new field in mm01 basic data screen,i added that field in basic data screen but when i create a material the data for that field will not save in database table.
Thanks,
murali.

Hi Murali,
when created added a field on the screen by using user exit then after that you have add the field in main table where you will be getting these table in the userexit only, please make sure about this. And i am sure defenitly it will get updated in to the table.
reward if useful.
thanks
abdulsamee.

I am trying to upload the purchase order long text in mm01 using BAPI

Hi All,
I am trying to upload Purchase Order Long text (which is in chinese Language) and Language field with ZH(chinese) in MM01 using BAPI_MATERIAL_SAVEDATA.
It is uploading properly, But in the Language field it is showing Z1(Customer reserve) instead of ZH(Chinese).
What could be the reason for this and how it can be resolved.
Thanks in advance,
Raja

Hi,
Which input parametr did you use? See table T002
LANGU = '1'
LAISO = 'ZH'
Rgds,
JP

Manual Layout data not saving to trx cube

Hello BPS Experts,
I am trying to load some data using manual planning. I open the layout and enter the values and press save. I do not find any requests / data in the cube.
case 1) No error / warning
I do not get any error during the save function in the layout. What could be the possible step I am missing. What could be the root cause..
case 2) message - No data to be saved
sometimes i get a message 'No data to be saved'. And that data is not getting saved. What could be the reason of this message.
Regards,
BWer
Message was edited by: BWer

Hello BWer,
One of the main reasons for data not saving from a layout into a Trx cube, is if there is no key figure being updated. The value of the key figure being posted should <> 0.
If you choose the option to display transaction data in your layout, then, only data with key figure values <> 0 will be displayed.
Sunil

TRX F150 -Dunning

Dear colleagues,
Further to the lauch of trx F150 for dunning I get a spool and I could print it but I need to turn it into a pdf and send it to an e-mail customer's address.
In case I have a spool that has several reminders for payment relating to different customers, there is a problem! That, because of the fact I can't share a document for 2 or more receivables and I can't send it to each customer by mail.
How can I solve this problem?
Thanks in advance.
Luca Stella

Dear friend
Agreed. However, live situation is User has performed Dunning run for all customer by mistake, where is not suppose to. and this dunning run is ended up with "Duning printout terminated" error.
If we fix the termination reason and complete the dunning then all outputs will go to customers automatically by e-mails from SAP. and we want to stop this.
hope I am clear and the requirment we are looking at...
best reg
S. Habib Pasha.

Trx F-53, The difference is too large for clearing Message no. F5263

Hi,
I created a PO, then I posted the goods receipt, the invoice and I was trying to
post the payment by F-53 trx.
When I select an open item from the list and I try to simulate the posting by the menu (Document, simulate), system replies by:
"*The difference is too large for clearing
Message no. F5263*"
Cannot understand why it is not possible to post the outgoing payment
Regards

Dear Sappione,
did You check the tolerances?
Check in transaction OBY6 the indicator 'No forex rate diff. when
clearing in LC' is not set the amount is converted with the exchange
rate valid at clearing date, in case You're clearing in LC a foreign document.
When you post a clearing transaction with rounding
differences, those differences are posted to an additional line item
GL accounts. This account determination is customized as follows :
FBKP - Exchange rate differences -
Exchange rate difference in open items - KDF -a/c XXXXXXXXX
(Realized gain exchange rate difference)
The accounts used for rounding differences when clearing
are the realized gain/loss exchange rate accounts.
please check all the 3 suggestions.
Mauri

How to add a new field in MM01, with say contaminent as a field?

How to add a new field in MM01, with say contaminent as a field? I process that i know is i has to go the user exit and check out the three user exits that are available for MM01 after that what i have to do please can any one help me out with the procedure to proceed?

Hai venkateshwar reddy ,
try with these user exits
MGA00001 Material Master (Industry): Checks and Enhancements
MGA00002 Material Master (Industry): Number Assignment
MGA00003 Material Master (Industry and Retail): Number Display
Refer these steps also
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/screen-exit-on-mm01-mm02-mm03-322717#

Set cursor in a specific view of transaction MM01/MM02

Hi,
We have to check a condition in the user-exit EXIT_SAPLMGMU_001, for transaction MM01/MM02, and if the condition fails the client wants to set the cursor in a specific field from a specific view. Is it possible? I tried to use the sentence SET CURSOR referenced to a remote program but it doesn't work.
Does anybody knows how to solve this problem?
Thanks in advance
Regards
Maribel

Hi
I hope, you have read the documetation attached with this Standard Enhancement - MGA00001.
EXIT_SAPLMGMU_001
Where Is the Customer Exit - EXIT_SAPLMGMU_001 called?
The customer exit is in function module MATERIAL_UPDATE_ALL. The
function module checks the data for errors (logical relationships,
foreign keys, fixed domain values, and so on) when the material master
is updated.
Use
o New fields
You can make checks possible for new fields of your own. These
checks must be identical to the checks that you carry out for your
new fields in online maintenance.
o Existing fields
For existing fields, you can extend and intensify the checks.
You can also change data for descriptions and general material data
(MARA). For example, the descriptions can be generated from attributes
of the material.
Limitations
You cannot bypass existing checks.
Interface to Application
The respective data of the current logical transaction is contained in
the structures, for example, in structure WMARA for MARA. Nonrelevant
structures are transferred with their initial values.
General material data that can be changed (CMARA) has the structure
MARU. This MARA view contains fewer internal fields than MARA itself. If
WMARA is filled, CMARA is also filled when accessed.
The customer exit contains the exception APPLICATION_ERROR for your
self-defined error situations.
Using the language element MESSAGE .. RAISING APPLICATION_ERROR, you can
terminate the current (logical) transaction and display your message in
the log.
Also, I guess, have you put some code in the Includes available with the EXITS and then activated the Project in CMOD.
Reward points
Regards

Select a specific view in MM02/MM01

Hi Abappers,
I am doing a BDC on MM01 transaction and want to just select the accounting view and extend materials for different valuation types. But the position of accounting view is coming different on different material and my BDC recording is failing to select the accounting view. Does anyone has any idea how we can pinpoint and select the accounting view?
Thanks,
David.

SELECTION_VIEWS_FIND - This FM Will work depends on material type..
in your case this FM Is not required and you need to have Accounting view.
Any way See below program and you will get some idea and uploaded data into Material master change mode and it is applicable to user defined view
REPORT zjpmuim306 NO STANDARD PAGE HEADING LINE-SIZE 250 MESSAGE-ID
zjpm001.
*& I N B O U N D V I A A B A P : Batch input Session method *
*& Development ID: IM_DD_306_LJP *
*& Report : ZJPMUIM306 *
*& The Purpose of the Object is to interface Create Input Record *
*& for SAP Migration from the Material master of BPCS All the *
*& information received at BPCS is collected into a single record. *
*& By using session method upload data from file ,one item is
*& created for one record *
*& Change Log: *
*& Init Who Date Text *
*& MALIKDH1 Seshu Reddy 26-07-2003 Initial Version *
 Constants *
CONSTANTS:c_vkorg(4) type c value 'JP20', " Sales Organization
 c_vtweg(2) type c value 'TR' , " Distribution Channel
 c_werks(4) Type c value 'JP01' , " Plant
 c_viewlist(15) VALUE 'KDEALBSZXVPCFQG'," View list
 c_scm_view TYPE msichtausw-dytxt VALUE 'SCM View',
 c_sd_view TYPE msichtausw-dytxt VALUE 'SD View',
 c_seq_code(2) VALUE 'Z1', " Sequential Code
 c_keep(1) TYPE c VALUE 'X', " Keep
 c_group LIKE apqi-groupid VALUE 'IM306', " Session Name
 c_tcode LIKE tstc-tcode VALUE 'MM02', " Transaction Code
 c_blank(1) VALUE ' ', " Blank
 c_intls(1) VALUE 'N'. " Logistic Status
 Variables *
DATA: g_flag1(1), " Variable to hold
 g_flag(1), " Variable to hold
 g_file LIKE rlgrap-filename VALUE
 'C:\Documents and Settings\seshur\Desktop\HCLT123.CSV'. " File name
 Internal tables/ Work area *
Internal Table for Delimter
DATA : BEGIN OF t_delim OCCURS 0,
 text(1000),
 END OF t_delim.
Internal table for BDC processing
DATA : t_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
Internal table for holding the data which has to be uploaded.
DATA: BEGIN OF t_bpcs OCCURS 0,
 matnr(15) TYPE c, " material no
 dosage(40) TYPE c, " Dosage form(Local)
 appearance(40) TYPE c, " Appearance
 idcode(6) TYPE c, " Identification Code
 prostformno(10) TYPE c, "SOP
 weitab(7) TYPE c, " Weight/tablet
 uom1(2) TYPE c, " UOM of Carton
 uom2(2) TYPE c, " UOM of Case
 carsize(14) TYPE c, " Carton size
 cassize(14) TYPE c, " Case size
 rupqty(11) TYPE c, " Round up
 abvname(3) TYPE c, " Product short name
 END OF t_bpcs.
*Internal table for t_bpcs
DATA: BEGIN OF t_mdata OCCURS 0,
 matnr LIKE marc-matnr, " Material number
 zzjp_dos_frm LIKE marc-zzjp_dos_frm, " Dosage form(Local)
 zzjp_aprn LIKE marc-zzjp_aprn, " Appearance
 zzjp_con_id LIKE marc-zzjp_con_id," Identification Code
 zzjp_nyu_sop LIKE marc-zzjp_nyu_sop,"SOP
 zzjp_wei_tab(10) type c , " Weight/tablet
 zzjp_bio LIKE marc-zzjp_bio,"Biologics Indicator
 zzjp_itf LIKE marc-zzjp_itf, " ITF code
 zzjp_car(2) type c, " UOM of Carton
 zzjp_cas(2) type c, " UOM of Case
 zzjp_car_size(11) type c," Carton size
 zzjp_cas_size(11) type c, " Case size
 zzjp_rupqty(11) type c, " Round up
 zzjp_init_ls LIKE marc-zzjp_init_ls, " Logistic Status
 zzjp_re1 LIKE marc-zzjp_re1, "Document type(Local)
 zzjp_re2 LIKE marc-zzjp_re2, "Report type
 zzjp_re3 LIKE marc-zzjp_re3, "Shipping report type
 zzjp_pro_id LIKE mvke-zzjp_pro_id," Product output sequence
 zzjp_bu_id LIKE mvke-zzjp_bu_id, " Business unit indicator
 zzjp_abv_name LIKE mvke-zzjp_abv_name," Product short name
 zzjp_abv_id1 LIKE mvke-zzjp_abv_id1," Product short name output
 zzjp_abv_id2 LIKE mvke-zzjp_abv_id2," Product short name internal
 zzjp_spl_id LIKE mvke-zzjp_spl_id, " Sample internal order
 END OF t_mdata.
Internal table for Mara Table
DATA: BEGIN OF t_mara OCCURS 0,
 matnr LIKE mara-matnr, " material Number
 vpsta LIKE mara-vpsta, " Maintenance status of complete material
 pstat like mara-pstat, " Maintenance status
 END OF t_mara.
Internal table for Material Master View Selection Screens
DATA: BEGIN OF t_bildtab OCCURS 0.
 INCLUDE STRUCTURE mbildtab.
DATA: END OF t_bildtab.
internal table for T_bildtab
DATA: t_bildtab_dup LIKE t_bildtab OCCURS 0 WITH HEADER LINE.
*Work area for T_bildtab internal table(Views Selection)
DATA: BEGIN OF w_data,
 flag1 type c,
 anzd70 TYPE i,
 field1(20) type c,
 field2(20) type c,
 field3(20) type c,
 field4(20) type c,
 count(2) TYPE c,
 END OF w_data.
 Main Processing *
START-OF-SELECTION.
Store data from file into internal table
PERFORM f_uplaod_data.
Transfer the uploaded data into t_mdata internal Table
PERFORM f_process_data.
Selecting The views based on Material number
PERFORM f_view_list.
Open a BDC Session
PERFORM f_bdc_open.
*Selecting the fields from mara table
SELECT matnr
 vpsta
 pstat
 FROM mara
INTO TABLE t_mara
FOR ALL ENTRIES IN t_mdata
WHERE matnr = t_mdata-matnr.
SORT t_mara BY matnr.
SORT t_mdata BY matnr.
Transfer the uploaded data into BDCDATA structure
PERFORM f_process_bdc.
Close The BDC Session
PERFORM f_close_group.
*& Form F_VIEW_LIST *
 Routine to used for Calling the function module *
 Selection_views_find *
FORM f_view_list.
CALL FUNCTION 'SELECTION_VIEWS_FIND'
 EXPORTING
 bildsequenz = c_seq_code
 pflegestatus = c_viewlist
 TABLES
 bildtab = t_bildtab
 EXCEPTIONS
 call_wrong = 1
 empty_selection = 2
 OTHERS = 3.
IF sy-subrc <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " F_VIEW_LIST
*& Form f612_view_sort *
Routine to used for Selecting The views based on Material Number *
FORM f612_view_sort.
t_bildtab_dup[] = t_bildtab[].
Reading the Internal table t_mara
READ TABLE t_mara WITH KEY matnr = t_mdata-matnr.
TRANSLATE t_mara-pstat USING ' $'.
CLEAR: w_data-flag1, w_data-anzd70.
LOOP AT t_bildtab_dup.
 IF t_bildtab_dup-pstat CA t_mara-pstat.
 w_data-anzd70 = w_data-anzd70 + 1.
 IF t_bildtab_dup-kzanz IS INITIAL.
 t_bildtab_dup-kzanz = 'X'.
 w_data-flag1 = 'X'.
 MODIFY t_bildtab_dup.
 ENDIF.
 ELSE.
 IF NOT t_bildtab_dup-kzanz IS INITIAL.
 CLEAR t_bildtab_dup-kzanz.
 w_data-flag1 = 'X'.
 MODIFY t_bildtab_dup.
 ENDIF.
 ENDIF.
ENDLOOP.
TRANSLATE t_mara-pstat USING '$ '.
IF NOT w_data-flag1 IS INITIAL.
 SORT t_bildtab_dup BY kzanz DESCENDING idxbd ASCENDING.
ENDIF.
*Reading The internal table for T_bildtab_dup
READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
IF t_bildtab_dup-kzanz = 'X'.
 WRITE sy-tabix TO w_data-count.
 w_data-count = w_data-count + 2.
 IF w_data-anzd70 > 18.
 w_data-count = w_data-count - 18.
 ENDIF.
 CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field1.
 CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field2.
ENDIF.
READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
IF t_bildtab_dup-kzanz = 'X'.
 WRITE sy-tabix TO w_data-count.
 IF w_data-anzd70 > 18.
 w_data-count = w_data-count + 2.
 w_data-count = w_data-count - 18.
 ENDIF.
 CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field3.
 CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field4.
ENDIF.
ENDFORM. " f612_view_sort
*& Form f_uplaod_data *
Routine to used for Uploading the data from file to Internal table *
FORM f_uplaod_data.
CALL FUNCTION 'WS_UPLOAD'
 EXPORTING
 filename = g_file
 filetype = 'DAT'
 TABLES
 data_tab = t_delim
 EXCEPTIONS
 conversion_error = 1
 file_open_error = 2
 file_read_error = 3
 invalid_type = 4
 no_batch = 5
 unknown_error = 6
 invalid_table_width = 7
 gui_refuse_filetransfer = 8
 customer_error = 9
 OTHERS = 10.
IF sy-subrc <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF t_bpcs IS INITIAL.
 LOOP AT t_delim.
 SPLIT t_delim-text AT ',' INTO t_bpcs-matnr
 t_bpcs-dosage
 t_bpcs-appearance
 t_bpcs-idcode
 t_bpcs-prostformno
 t_bpcs-weitab
 t_bpcs-uom1
 t_bpcs-uom2
 t_bpcs-carsize
 t_bpcs-cassize
 t_bpcs-rupqty
 t_bpcs-abvname.
 APPEND t_bpcs.
 ENDLOOP.
ENDIF.
ENDFORM. " f_uplaod_data
*& Form F_BDC_OPEN
 Routine to create BDC Session to be processed
FORM f_bdc_open.
CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING
 client = sy-mandt
 group = c_group
 keep = c_keep
 user = sy-uname
 EXCEPTIONS
 client_invalid = 1
 destination_invalid = 2
 group_invalid = 3
 group_is_locked = 4
 holddate_invalid = 5
 internal_error = 6
 queue_error = 7
 running = 8
 system_lock_error = 9
 user_invalid = 10
 OTHERS = 11.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
MESSAGE S000 WITH 'Batch input session is created successfully'(T02).
ENDIF.
ENDFORM. " F_BDC_OPEN
*& Form F_PROCESS_BDC
 Processing of BDCDATA Structure
FORM f_process_bdc.
LOOP AT t_mdata.
 PERFORM f612_view_sort.
 PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0060'.
 PERFORM f_bdc_field USING 'BDC_CURSOR'
 'RMMG1-MATNR'.
 PERFORM f_bdc_field USING 'BDC_OKCODE'
 '=AUSW'.
 PERFORM f_bdc_field USING 'RMMG1-MATNR'
 t_mdata-matnr.
 PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0070'.
 PERFORM f_bdc_field USING 'BDC_CURSOR'
 'MSICHTAUSW-DYTXT(01)'.
 IF w_data-anzd70 > 18.
 PERFORM f_bdc_field USING 'BDC_OKCODE'
 '=P+'.
 PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0070'.
 PERFORM f_bdc_field USING 'BDC_OKCODE' '/00'.
 ENDIF.
reading the t_bildtab internal table
 READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
 IF t_bildtab_dup-kzanz = 'X'.
 PERFORM f_bdc_field USING 'BDC_CURSOR'
 w_data-field1.
 PERFORM f_bdc_field USING w_data-field2 'X'.
 g_flag = 'X'.
 ENDIF.
reading the t_bildtab internal table
 READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
 IF sy-subrc EQ 0.
 g_flag = 'X'.
 ENDIF.
 IF t_bildtab_dup-kzanz = 'X'.
 PERFORM f_bdc_field USING 'BDC_CURSOR'
 w_data-field3.
 PERFORM f_bdc_field USING w_data-field4 'X'.
 g_flag1 = 'X'.
 ENDIF.
 IF g_flag = 'X' AND g_flag1 = 'X'.
 PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0080'.
 PERFORM f_bdc_field USING 'BDC_CURSOR'
 'RMMG1-VTWEG'.
 PERFORM f_bdc_field USING 'BDC_OKCODE'
 '=ENTR'.
 PERFORM f_bdc_field USING 'RMMG1-WERKS'
 c_werks.
 PERFORM f_bdc_field USING 'RMMG1-VKORG'
 c_vkorg.
 PERFORM f_bdc_field USING 'RMMG1-VTWEG'
 c_vtweg.
 CLEAR g_flag.
 CLEAR g_flag1.
 ELSE.
 IF g_flag = 'X'.
 PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0080'.
 PERFORM f_bdc_field USING 'RMMG1-WERKS'
 c_werks.
 PERFORM f_bdc_field USING 'BDC_OKCODE' '/00'.
 ELSE.
 IF g_flag1 = 'X'.
 PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0080'.
 PERFORM f_bdc_field USING 'BDC_CURSOR'
 'RMMG1-VTWEG'.
 PERFORM f_bdc_field USING 'RMMG1-WERKS'
 c_werks.
 PERFORM f_bdc_field USING 'RMMG1-VKORG'
 c_vkorg.
 PERFORM f_bdc_field USING 'RMMG1-VTWEG'
 c_vtweg.
 PERFORM f_bdc_field USING 'BDC_OKCODE'
 '=ENTR'.
 ENDIF.
 ENDIF.
 ENDIF.
*Processing of SCM View
 PERFORM f_bdc_dynpro USING 'SAPLMGMM' '4000'.
 PERFORM f_bdc_field USING 'BDC_CURSOR' 'MARC-ZZJP_DOS_FRM'.
 PERFORM f_bdc_field USING 'MARC-ZZJP_DOS_FRM'
 t_mdata-zzjp_dos_frm.
 PERFORM f_bdc_field USING 'MARC-ZZJP_APRN'
 t_mdata-zzjp_aprn.
 PERFORM f_bdc_field USING 'MARC-ZZJP_CON_ID'
 t_mdata-zzjp_con_id.
 PERFORM f_bdc_field USING 'MARC-ZZJP_NYU_SOP'
 t_mdata-zzjp_nyu_sop.
 PERFORM f_bdc_field USING 'MARC-ZZJP_WEI_TAB'
 t_mdata-zzjp_wei_tab.
 PERFORM f_bdc_field USING 'MARC-ZZJP_CAR'
 t_mdata-zzjp_car.
 PERFORM f_bdc_field USING 'MARC-ZZJP_CAS'
 t_mdata-zzjp_cas.
 PERFORM f_bdc_field USING 'MARC-ZZJP_CAR_SIZE'
 t_mdata-ZZJP_CAR_SIZE.
 PERFORM f_bdc_field USING 'MARC-ZZJP_CAS_SIZE'
 t_mdata-ZZJP_CAS_SIZE.
 PERFORM f_bdc_field USING 'MARC-ZZJP_RUPQTY'
 t_mdata-ZZJP_RUPQTY.
 PERFORM f_bdc_field USING 'MARC-ZZJP_BIO'
 t_mdata-zzjp_bio.
 PERFORM f_bdc_field USING 'MARC-ZZJP_ITF'
 t_mdata-zzjp_itf.
 PERFORM f_bdc_field USING 'MARC-ZZJP_INIT_LS'
 t_mdata-zzjp_init_ls.
 PERFORM f_bdc_field USING 'MARC-ZZJP_RE1'
 t_mdata-zzjp_re1.
 PERFORM f_bdc_field USING 'MARC-ZZJP_RE2'
 t_mdata-zzjp_re2.
 PERFORM f_bdc_field USING 'MARC-ZZJP_RE3'
 t_mdata-zzjp_re3.
 PERFORM f_bdc_field USING 'BDC_OKCODE'
 '/00'.
*Processing of SD View
 PERFORM f_bdc_dynpro USING 'SAPLMGMM' '4000'.
 PERFORM f_bdc_field USING 'BDC_CURSOR' 'MVKE-ZZJP_PRO_ID'.
 PERFORM f_bdc_field USING 'MVKE-ZZJP_PRO_ID'
 t_mdata-zzjp_pro_id.
 PERFORM f_bdc_field USING 'MVKE-ZZJP_BU_ID'
 t_mdata-zzjp_bu_id.
 PERFORM f_bdc_field USING 'MVKE-ZZJP_ABV_NAME'
 t_mdata-zzjp_abv_name.
 PERFORM f_bdc_field USING 'MVKE-ZZJP_ABV_ID1'
 t_mdata-zzjp_abv_id1.
 PERFORM f_bdc_field USING 'MVKE-ZZJP_ABV_ID2'
 t_mdata-zzjp_abv_id2.
 PERFORM f_bdc_field USING 'MVKE-ZZJP_SPL_ID'
 t_mdata-zzjp_spl_id.
 PERFORM f_bdc_field USING 'BDC_OKCODE' '/00'.
 PERFORM f_bdc_dynpro USING 'SAPLSPO1' '0300'.
 PERFORM f_bdc_field USING 'BDC_OKCODE'
 '=YES'.
perform f_bdc_insert.
REFRESH T_BDCDATA.
ENDLOOP.
ENDFORM. " F_PROCESS_BDC
*& Form f_bdc_dynpro
p_prog is the program name to which data is passed *
p_dyno is the screen number to which the data is passed
 Routine for populating the BDCDATA structure with the
 Screen related information
FORM f_bdc_dynpro USING p_prog
 p_dyno.
t_bdcdata-program = p_prog.
t_bdcdata-dynpro = p_dyno.
t_bdcdata-dynbegin = 'X'.
APPEND t_bdcdata.
CLEAR t_bdcdata.
ENDFORM. " F_bdc_dynpro
*& Form F_BDC_FIELD
 p_fnam is the field name to which value is passed
 p_fval is the field value which is passed
 p_fnam is the field name to which value is passed
 p_fval is the field value which is passed
FORM f_bdc_field USING p_fnam
 p_fval.
t_bdcdata-fnam = p_fnam.
t_bdcdata-fval = p_fval.
APPEND t_bdcdata.
CLEAR t_bdcdata.
ENDFORM. " F_bdc_field
*& Form F_PROCESS_DATA *
 Routine to used for moving data from T_bpcs internal table to *
 t_mdata Internal Table *
FORM f_process_data.
LOOP AT t_bpcs.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = t_bpcs-matnr
 IMPORTING
 output = t_mdata-matnr.
 MOVE t_bpcs-dosage TO t_mdata-zzjp_dos_frm.
 MOVE t_bpcs-appearance TO t_mdata-zzjp_aprn.
 MOVE t_bpcs-idcode TO t_mdata-zzjp_con_id.
 MOVE t_bpcs-prostformno TO t_mdata-zzjp_nyu_sop.
 MOVE t_bpcs-weitab TO t_mdata-zzjp_wei_tab.
 MOVE c_blank TO t_mdata-zzjp_bio.
 MOVE c_blank TO t_mdata-zzjp_itf.
 MOVE t_bpcs-uom1 TO t_mdata-zzjp_car.
 MOVE t_bpcs-uom2 TO t_mdata-zzjp_cas.
 MOVE t_bpcs-carsize TO t_mdata-zzjp_car_size.
 MOVE t_bpcs-cassize TO t_mdata-zzjp_cas_size.
 MOVE t_bpcs-rupqty TO t_mdata-zzjp_rupqty.
 MOVE c_intls TO t_mdata-zzjp_init_ls.
 MOVE c_blank TO t_mdata-zzjp_re1.
 MOVE c_blank TO t_mdata-zzjp_re2.
 MOVE c_blank TO t_mdata-zzjp_re3.
 MOVE c_blank TO t_mdata-zzjp_pro_id.
 MOVE c_blank TO t_mdata-zzjp_bu_id.
 MOVE t_bpcs-abvname TO t_mdata-zzjp_abv_name.
 MOVE c_blank TO t_mdata-zzjp_abv_id1.
 MOVE c_blank TO t_mdata-zzjp_abv_id2.
 MOVE c_blank TO t_mdata-zzjp_spl_id.
 APPEND t_mdata.
ENDLOOP.
ENDFORM. " F_PROCESS_DATA
*& Form f_bdc_close
 Routine to close the BDC Session
FORM f_close_group.
CALL FUNCTION 'BDC_CLOSE_GROUP'
 EXCEPTIONS
 not_open = 1
 queue_error = 2
 OTHERS = 3.
IF sy-subrc <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " f_close_group
*& Form f_bdc_insert
 routine to input batch data into the Transaction MM02 from the
 session created
FORM f_bdc_insert.
CALL FUNCTION 'BDC_INSERT'
 EXPORTING
 tcode = c_tcode
 TABLES
 dynprotab = t_bdcdata
 EXCEPTIONS
 internal_error = 1
 not_open = 2
 queue_error = 3
 tcode_invalid = 4
 printing_invalid = 5
 posting_invalid = 6
 OTHERS = 7.
 IF sy-subrc <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
ENDFORM. " f_bdc_insert
Reward Points if it is helpful
Thanks
Seshu

How to make a field default in mm01 while coping from other material

hi all,
i want to make a field default in mm01 ....mara-mstae -
say value 'A', when
i am coping from other material.
normally a T.variant is working in the scenario when im creating a material
but not when i am coping from other material.
Any field exits would work on that .if so how?
thanks in advance,\
sg

i have to make the x-plant material status as 'BE' in mm01 basic view 1 ,when the material is created or copied from .but it should be only default for the user might change it
now when the material was created its workin---- coz a transaction variant has been created.
but when im coping it from other material its picking the properties of the old material ( from which im coping) ..not the field value which i want to display as default.
field exit only validates. can we give default value by it ,before saving a material??????
thanks,
sg

Error while loading new trx types to a new OU

Steps to reproduce:
Please note, source and target instance are same here
1. Assume X is the existing OU, and Y is the new OU setup at basic level
2. Dowloaded Receivables trx types data as an extract for OU = X
3. Modified the xml file to point it to new OU = Y
4. Re-uploaded the extract to iSetup
5. Used this new extract to perform a load in the same instance
6. Below error received.
Can you pls review and help me soon.
The following exception has occured while processing:
Object Name : Cust Trx Types
Record Identifiers : <Name> = 'Credit Memo'
Exception : Exception occurred in API 'Transaction Types API.'
Entity 'CustTrxTypeEO'
<Name> = 'Credit Memo'
<Business Group Name> = 'Setup Business Group'
<Org Name> = 'iSetup OU'
java.lang.NullPointerException
 at java.lang.String.<init>(String.java:147)
 at oracle.apps.ar.ispeed.transactionType.server.CustTrxTypeEOImpl.initialize(CustTrxTypeEOImpl.java:996)
 at oracle.apps.ar.ispeed.transactionType.server.CustTrxTypeEOImpl.doDML(CustTrxTypeEOImpl.java:1898)
 at oracle.jbo.server.EntityImpl.postChanges(EntityImpl.java:4530)
 at oracle.apps.fnd.framework.server.OAEntityImpl.postChanges(OAEntityImpl.java:1759)
 at oracle.apps.az.fwk.server.BEEntityImpl.postChanges(BEEntityImpl.java:230)
 at oracle.apps.az.fwk.server.BEImport.validateOneRecord(BEImport.java:1962)
 at oracle.apps.az.fwk.server.BEImport.endElement(BEImport.java:759)
 at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1318)
 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336)
 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:205)
 at oracle.apps.az.fwk.server.BEImport.importXML(BEImport.java:377)
 at oracle.apps.az.fwk.server.BEApplicationModuleImpl.importFromXML(BEApplicationModuleImpl.java:401)
 at oracle.apps.az.r12.api.BC4JAPI.importAPI(BC4JAPI.java:857)
 at oracle.apps.az.r12.loader.cpserver.APILoader$APIExecuter.run(APILoader.java:648)

If you are on R12, please apply the patches in these two docs and check then.
iSetup: Imported Transaction Types Using iSetup Populates ORG_ID Value In Legal Entity Field [ID 1340427.1]
R12.1: Loading Payables Option Extract into Target Fails with the Following Exception: java.lang.NullPointerException [ID 1323037.1]
Also, make sure you have all the recommended patches applied.
Isetup List Of Mandatory Patches For R12 [ID 811040.1]
iSetup Mandatory Patches post 12.1.1 [ID 857551.1]
iSetup Mandatory Patches for 11.5.10.2 [ID 1317257.1]
11.5.10.2 isetup mandatory patches [ID 1337228.1]
Thanks,
Hussein

Trx MM01.

Similar Messages

Maybe you are looking for