Material Update
Sir,
When i update material then a massage came out.
Massege is
Posting onily possible in period 2009/02 and 2009/01 in country code xxxxx
Message No. M7053
Diagnosis
The posting date entered is not within one of the permitted posting period (current period/previous period).
This can be due to one of two reasons:
The correct current period has not been set in the system.
For the system, the first of the entered periods is the current period. At the beginning of a new period, your systems administrator must change current the period in the material master record, using the function "Shift periods". This has not yet been done.
You hane entered a worng date inthe "Posting date".
Pocedure
Check the posting date and correct it if necessary. If your input is correct, inform your systems administrator that the "period shifting" (period- end closing) process has not yet been completed.
Pls help me in details
Thanking you in advance
Hi
It seems the MM period is open only for Jan & Feb'09 and you are trying to post in Mar'09. You can confirm this in OMSY
To open the MM period try MMPV
Also confirm FI period for Mar'09 is open in OB52
Thank You,
Similar Messages
-
Material Updates from ECC to CRM
Hi Experts,
We recently had application of Enhancement Pack4 on our ECC system. After the application EHP4 pack, we have started getting some material updates from ECC to CRM. And those updates are failing in CRM as we do not have any material set up in CRM. Due to these failed updates, lot of dumps are getting created in CRM. So can u please advice where/how in ECC i can restrict these updates to go to CRM. Any help in this will be highly appreciable.
Regards
CharithaHello Charitha,
In txnn:R3AC4 of CRM , check INACTIVE flag for object MATERIAL (and any other objects whose data is not required in CRM)
for your RFC destination (ECC).
This would prevent any automatic data flow for this object from R/3 to CRM.
Hope this helps!
Best Regards,
Shanthala Kudva. -
Bom & Material update into others plant automatically
Hi Experts
How it is possible to extend in a simple way into other plant .
suppose i am creating one BOM in Plant A and want to extend into B,C,D,E simultaneously .
and also easiest way to Extend Material with one plant to another plant with minimum effort by user.
Rgds
Pankaj AgarwalHi,
It is not possible to update automatically in standard SAP.
Either you can go for custom program or use standard LSMW object for extending the master data in the other plants
As usual, the same template what ever used for Material and BOM creation initially can be used.
Thanks
Ram Vepuri -
Std price of material updation in SAP system
dear all
I had created a material CLC Block in material master & had mention the Std price for the same. say 28 rs/unit
Then i had change the std price for that particular material by T-code MR21.
say 30 rs/unit.
the system shows the updated new price for that material in Master, but when we make GRN for the same material by movememt type 501 q, the system takes the old pirce only. ie 28 rs/unit.
the cost gets book w.r.t old price only.
pls help me out in this mater in detail.
thank in advance to all SAP experts
regard
parikshithi
udo
thanks for your valuable input.
I had test the procedure what you had explain.
i had assign the price w.r.t WBS no & it works
thanks once again
regards
parikshit -
Hello,
I've include a new subscreen for the material master transactions.
When I'm updating the material using MM02 and I only make changes in my custom fields the transaction doesn't go through the exit in which I've placed the code to save them.
Is there any way to put some code in one of my PAI modules in order to solve this issue?
Thanks in advance!Hi,
Just to recap, X-dist chain status is generally used in different purpose rather than conditions.
Whenver new material is created with sales views. its CO-Controlling directives that until the costing of the material is not done, there should not be any sales. Thus, they restrict the sales of this material with this field.
Once costing is done, this material will be ready for sale & then this field will be removed ( there are various ways to remove/blank this field in SAP).
same concept is exist, to procure the material also.
Let me know, the prupose- why you want to use this field in your requirement. Still if you would like to use, as said by mate, there is no automatic functionality to update this field. It has to be done manually or with some subsequent function.
Hope it helps.
Regards,
Reazuddin MD -
I want to update some customer fields on the Material Master MEAN table. I have added the append structure to the table. I want to update the fields when I call this BAPI
BAPI_MATERIAL_SAVEDATA
Is there a BADI available through this BAPI call where I can update this data ?The documentation for EXTENSIONIN tells me that I can only update the following
The structures BAPI_TE_<NAME> (<NAME> = MARA, MARC, MARD, MBEW, MLGN, MLGT, MVKE) and the relevant checkbox structures BAPI_TE_<NAME> (<NAME> = MARAX, etc.) must first be extended by the customer to include the fields required. The standard structures contain only the corresponding key fields. When including new fields in these structures, make sure that the field has the same name as the field in the database table. In addition, the fields in the structures BAPI_TE_<NAME> may only be of the type CHARACTER. The data element BAPIUPDATE must be used for the fields in the checkbox structure (except for key fields).
There is no BAPI_TE_MEAN structure to update which means I cannot pass it in EXTENSIONIN ? I assume ? -
Structure of the input file for RMDATIND (standard material update program)
Hi all !
I need to find the structure of the input file used by the RMDATIND standard program. Is there only one structure for this file ? what should it contains ?
Thanks a lot
Regards,
--YohannHi Yohann,
Check this link...
[RMDATIND Document|http://www.iconet-ltd.co.uk/mm.doc]
Hope this would solve your issue.
Regards
Narin Nandivada -
Updation not happening once after the material has been extened
Dear Guru's,
I want to extend materials from one plant to another plant. I am using BAPI_MATERIAL_SAVEDATA.
every thing is doing good but the material was updated in the destination plant. I have used BAPI_TRANSACTION_COMMIT' also. ans not all getting any any error message. In the return table i am getting success message. please help me. I am sending my code also. please gothrough and give suggestion . it very urgent.
points will be given for solving the problem.
Thanks in advance.
REPORT ZMMR_MATERIAL_EXTENSION.
TABLES: T001L, "Storage Locations
MARA, "General Material Data
MAKT, "Material Descriptions
MBEW, "Material Valuation
MARC, "Plant Data for Material
MARD. " Storage location
DATA : INDEX LIKE SY-TABIX.
DATA: BAPI_HEAD LIKE BAPIMATHEAD,
BAPI_MAKT LIKE BAPI_MAKT, "Material Description
BAPI_MARA1 LIKE BAPI_MARA, "Client Data
BAPI_MARAX LIKE BAPI_MARAX,
BAPI_MARC1 LIKE BAPI_MARC, "Plant View
BAPI_MARCX LIKE BAPI_MARCX,
BAPI_MBEW1 LIKE BAPI_MBEW, "Accounting View
BAPI_MBEWX LIKE BAPI_MBEWX,
BAPI_MARD1 LIKE BAPI_MARD, " STORAGE LOCATION
BAPI_MARDX LIKE BAPI_MARDX,
BAPI_RETURN LIKE BAPIRET2.
DATA: BEGIN OF INT_MAKT OCCURS 100.
INCLUDE STRUCTURE BAPI_MAKT.
DATA: END OF INT_MAKT.
for material updation*******
*data:mara_data type bapi_mara,
*mara_datax type bapi_marax,
*wa_bapi_te_mara type bapi_te_mara,
*wa_bapi_te_marax type bapi_te_marax,
*wa_valuepart(960),
*wa_valuepartx(960),
*t_extin type table of bapiparex,
*t_extinx type table of bapiparexx,
*d_extin type bapiparex,
*d_extinx type bapiparexx,
*ret type bapiret2.
DATA: BEGIN OF INT_MAT OCCURS 100,
WERKS(4), "Plant
MTART(4), "Material type
MATNR(18), "Material number
MATKL(9) , "Material group
MBRSH(1), "Industry sector
MEINS(3), "Base unit of measure
GEWEI(3), "Weight Unit
SPART(2), "Division
TRAGR(4), "Transportation group
EKWSL(4), "Purchasing Value Key
marc
EKGRP(3), "Purchasing group
MTVFP(2), "Checking Group for Availability Check
LADGR(4), "Loading group
PRCTR(10), "Profit Center
WEBAZ like BAPI_MARC-GR_PR_TIME, "Goods receipt processing time in days.
PERKZ(1), "Period indicator
AWSLS(6), "Variance Key
DISGR(4), "MRP Group
DISMM(2), "MRP Type
DISPO(3), "MRP controller
DISLS(2), "Lot size (materials planning)
BESKZ(1), "Procurement Type
DZEIT like BAPI_MARC-INHSEPRODT, "In-house production time.
PLIFZ like BAPI_MARC-PLND_DELRY, "Planned delivery time in days.
makt
SPRAS(2), "Language key
MAKTX(40), "Material description
***mbew
BKLAS(4), "Valuation Class.
VPRSV(1), "Price control indicator
VERPR like BAPI_MBEW-MOVING_PR, "Moving Average Price
STPRS like BAPI_MBEW-STD_PRICE, "Standard price
PEINH like BAPI_MBEW-PRICE_UNIT, "Price unit
****mard
LGORT(4), "Storage location
END OF INT_MAT.
SELECT-OPTIONS:
PLANT FOR MARC-WERKS OBLIGATORY MEMORY ID PLT,
MATERIAL FOR MARA-MATNR MEMORY ID MAT,
MATLTYPE FOR MARA-MTART MEMORY ID MTY,
DIVISION FOR MARA-SPART MEMORY ID DIV.
PARAMETERS: F_FILE LIKE RLGRAP-FILENAME
DEFAULT 'C:\DATA\ZMATERIAL.XLS' MEMORY ID F_FILE,
GETDATA AS CHECKBOX, "Tick to download materials data to local harddisk
UPDDATA AS CHECKBOX. "Tick to update date to Materials Master
IF GETDATA = 'X'.
PERFORM DOWNLOAD_DATA.
PERFORM DOWNLOAD_FILE.
ENDIF.
IF UPDDATA = 'X'.
PERFORM UPLOAD_FILE.
PERFORM UPDATE_MM.
ENDIF.
*& Form DOWNLOAD_DATA
text
FORM DOWNLOAD_DATA.
*IF MATLTYPE-LOW NE 'SFGD' OR MATLTYPE-LOW NE 'SPRS'.
SELECT * FROM MARC WHERE LVORM EQ ' '
AND WERKS IN PLANT
AND MATNR IN MATERIAL.
CLEAR MARA.
SELECT SINGLE * FROM MARA WHERE MATNR = MARC-MATNR .
CHECK MATLTYPE.
IF MARA-MTART = 'SFGD' or MARA-MTART = '' or MARA-MTART = 'SPRS'.
clear : MARA,INT_MAT.
continue.
ENDIF.
CHECK DIVISION.
CLEAR MBEW.
SELECT SINGLE * FROM MBEW WHERE MATNR = MARC-MATNR
AND BWKEY = MARC-WERKS.
CLEAR MAKT.
SELECT SINGLE * FROM MAKT WHERE SPRAS = 'EN'
AND MATNR = MARC-MATNR.
CLEAR MARD.
SELECT SINGLE * FROM MARD WHERE MATNR = MARC-MATNR
AND WERKS = MARC-WERKS.
WRITE:/ MARC-WERKS, "Plant
MARA-MTART, "Material type
MARA-MATNR, "Material number
MARA-MATKL, "Material group
MARA-MBRSH, "Industry sector
MARA-MEINS, "Base unit of measure
MARA-GEWEI, "Weight Unit
MARA-SPART, "Division
MARA-TRAGR, "Trasaction Group
MARA-EKWSL, "Purchase Value key
MARA-IPRKZ, "Period indi.for. SLED.
MARC-EKGRP, "Purchasing group
MARC-MTVFP, "Availability check
MARC-LADGR, "Loading grp.
MARC-PRCTR, "Profit Center
MARC-WEBAZ, "GR processing time
MARC-PERKZ, "Period Indicator
MARC-AWSLS, "Variance key
MARC-DISGR, "MRP GROUP
MARC-DISMM, "MRP TYPE
MARC-DISPO, "MRP CONTOLLER
MARC-DISLS, "LOT SIZE
MARC-BESKZ, "PROCUREMENT TYPE
MARC-DZEIT, "IN-HOUSE PRD TIME
MARC-PLIFZ, "PLANT DELIVERY TIME
MBEW-BKLAS, "VALUATION CLASS
MBEW-VPRSV, "Price control indicator
MBEW-VERPR, "MOVING PRICE
MBEW-STPRS, "Standard price
MBEW-PEINH, "Price unit
MAKT-SPRAS, "Language key
MAKT-MAKTX, "Material description
MARD-LGORT. "Storage location.
INT_MAT-WERKS = MARC-WERKS. "Plant
INT_MAT-MTART = MARA-MTART. "Material type
INT_MAT-MATNR = MARA-MATNR. "Material number
INT_MAT-MATKL = MARA-MATKL. "Material group
INT_MAT-MBRSH = MARA-MBRSH. "Industry sector
INT_MAT-MEINS = MARA-MEINS. "Base unit of measure
INT_MAT-GEWEI = MARA-GEWEI. "Weight Unit
INT_MAT-SPART = MARA-SPART. "Division
INT_MAT-TRAGR = MARA-TRAGR. "Trasaction Group
INT_MAT-EKWSL = MARA-EKWSL. "Purchase Value key
INT_MAT-IPRKZ = MARA-IPRKZ. "Period indi.for. SLED.
INT_MAT-EKGRP = MARC-EKGRP. "Purchasing group
INT_MAT-MTVFP = MARC-MTVFP. "Availability check
INT_MAT-LADGR = MARC-LADGR. "Loading grp.
INT_MAT-PRCTR = MARC-PRCTR. "Profit Center
INT_MAT-WEBAZ = MARC-WEBAZ. "GR processing time
INT_MAT-PERKZ = MARC-PERKZ. "Period Indicator
INT_MAT-AWSLS = MARC-AWSLS. "Variance key
INT_MAT-DISGR = MARC-DISGR. "MRP GROUP
INT_MAT-DISMM = MARC-DISMM. "MRP TYPE
INT_MAT-DISPO = MARC-DISPO. "MRP CONTOLLER
INT_MAT-DISLS = MARC-DISLS. "LOT SIZE
INT_MAT-BESKZ = MARC-BESKZ. "PROCUREMENT TYPE
INT_MAT-DZEIT = MARC-DZEIT. "IN-HOUSE PRD TIME
INT_MAT-PLIFZ = MARC-PLIFZ. "PLANT DELIVERY TIME
INT_MAT-BKLAS = MBEW-BKLAS. "Valution class
INT_MAT-VPRSV = MBEW-VPRSV. "Price control indicator
INT_MAT-VERPR = MBEW-VERPR. "Moving price
INT_MAT-STPRS = MBEW-STPRS. "Standard price
INT_MAT-PEINH = MBEW-PEINH. "Price unit
INT_MAT-SPRAS = MAKT-SPRAS. "Language key
INT_MAT-MAKTX = MAKT-MAKTX. "Material description
INT_MAT-LGORT = MARD-LGORT. " Storage location
APPEND INT_MAT.
CLEAR INT_MAT.
ENDSELECT.
*ENDIF.
ENDFORM. "DOWNLOAD_DATA
*& Form DOWNLOAD_FILE
text
FORM DOWNLOAD_FILE.
call function 'WS_DOWNLOAD'
EXPORTING
FILENAME = F_FILE
FILETYPE = 'DAT'
FILETYPE = 'WK1'
tables
data_tab = INT_MAT
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_WRITE_ERROR = 2
INVALID_FILESIZE = 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.
FORMAT COLOR COL_GROUP.
WRITE:/ 'Data Download Successfully to your local harddisk'.
SKIP.
ENDIF.
ENDFORM. "DOWNLOAD_FILE
*& Form UPLOAD_FILE
text
FORM UPLOAD_FILE.
call function 'WS_UPLOAD'
EXPORTING
FILENAME = F_FILE
FILETYPE = 'DAT'
FILETYPE = 'WK1'
tables
data_tab = INT_MAT
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_WRITE_ERROR = 2
INVALID_FILESIZE = 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.
FORMAT COLOR COL_GROUP.
WRITE:/ 'Data Upload Successfully from your local harddisk'.
SKIP.
ENDIF.
ENDFORM. "UPLOAD_FILE
*& Form UPDATE_MM
text
FORM UPDATE_MM.
LOOP AT INT_MAT.
Header
BAPI_HEAD-MATERIAL = INT_MAT-MATNR.
BAPI_HEAD-IND_SECTOR = INT_MAT-MBRSH.
BAPI_HEAD-MATL_TYPE = INT_MAT-MTART.
BAPI_HEAD-BASIC_VIEW = 'X'.
BAPI_HEAD-PURCHASE_VIEW = 'X'.
BAPI_HEAD-ACCOUNT_VIEW = 'X'.
BAPI_HEAD-MRP_VIEW = 'X'.
BAPI_HEAD-STORAGE_VIEW = 'X'.
BAPI_HEAD-QUALITY_VIEW = 'X'.
BAPI_HEAD-COST_VIEW = 'X'.
wa_bapi_te_mara-material = INT_MAT-MATNR.
wa_bapi_te_marax-material = INT_MAT-MATNR.
Material Description
REFRESH INT_MAKT.
INT_MAKT-LANGU = INT_MAT-SPRAS.
INT_MAKT-MATL_DESC = INT_MAT-MAKTX.
APPEND INT_MAKT.
sorage location.
BAPI_MARD1-PLANT = INT_MAT-WERKS.
BAPI_MARD1-STGE_LOC = INT_MAT-LGORT.
BAPI_MARDX-PLANT = INT_MAT-WERKS.
BAPI_MARDX-STGE_LOC = INT_MAT-LGORT.
Client Data - Basic
BAPI_MARA1-MATL_GROUP = INT_MAT-MATKL.
BAPI_MARA1-BASE_UOM = INT_MAT-MEINS.
BAPI_MARA1-UNIT_OF_WT = INT_MAT-GEWEI.
BAPI_MARA1-DIVISION = INT_MAT-SPART.
BAPI_MARA1-TRANS_GRP = INT_MAT-TRAGR.
BAPI_MARA1-PUR_VALKEY = INT_MAT-EKWSL.
BAPI_MARAX-MATL_GROUP = 'X'.
BAPI_MARAX-BASE_UOM = 'X'.
BAPI_MARAX-UNIT_OF_WT = 'X'.
BAPI_MARAX-DIVISION = 'X'.
BAPI_MARAX-TRANS_GRP = 'X'.
BAPI_MARAX-PUR_VALKEY = 'X'.
Plant - Purchasing
BAPI_MARC1-PLANT = INT_MAT-WERKS . "PLANT-LOW.
BAPI_MARC1-PUR_GROUP = INT_MAT-EKGRP.
BAPI_MARC1-AVAILCHECK = INT_MAT-MTVFP.
BAPI_MARC1-LOADINGGRP = INT_MAT-LADGR.
BAPI_MARC1-PROFIT_CTR = INT_MAT-PRCTR. " profit center and plant are same
BAPI_MARC1-GR_PR_TIME = INT_MAT-WEBAZ.
BAPI_MARC1-PERIOD_IND = INT_MAT-PERKZ.
BAPI_MARC1-VARIANCE_KEY = INT_MAT-AWSLS.
BAPI_MARC1-MRP_GROUP = INT_MAT-DISGR.
BAPI_MARC1-MRP_TYPE = INT_MAT-DISMM.
BAPI_MARC1-MRP_CTRLER = INT_MAT-DISPO.
BAPI_MARC1-LOTSIZEKEY = INT_MAT-DISLS.
BAPI_MARC1-PROC_TYPE = INT_MAT-BESKZ.
BAPI_MARC1-INHSEPRODT = INT_MAT-DZEIT.
BAPI_MARC1-PLND_DELRY = INT_MAT-PLIFZ.
BAPI_MARCX-PLANT = INT_MAT-WERKS . " PLANT-LOW.
BAPI_MARCX-PUR_GROUP = 'X'.
BAPI_MARCX-AVAILCHECK = 'X'.
BAPI_MARCX-LOADINGGRP = 'X'.
BAPI_MARCX-PROFIT_CTR = 'X'.
BAPI_MARCX-GR_PR_TIME = 'X'.
BAPI_MARCX-PERIOD_IND = 'X'.
BAPI_MARCX-VARIANCE_KEY = 'X'.
BAPI_MARCX-MRP_GROUP = 'X'.
BAPI_MARCX-MRP_TYPE = 'X'.
BAPI_MARCX-MRP_CTRLER = 'X'.
BAPI_MARCX-LOTSIZEKEY = 'X'.
BAPI_MARCX-PROC_TYPE = 'X'.
BAPI_MARCX-INHSEPRODT = 'X'.
BAPI_MARCX-PLND_DELRY = 'X'.
Accounting
BAPI_MBEW1-VAL_AREA = INT_MAT-WERKS.
BAPI_MBEW1-VAL_CLASS = INT_MAT-BKLAS.
BAPI_MBEW1-PRICE_CTRL = INT_MAT-VPRSV.
BAPI_MBEW1-MOVING_PR = INT_MAT-VERPR.
BAPI_MBEW1-STD_PRICE = INT_MAT-STPRS.
BAPI_MBEW1-PRICE_UNIT = INT_MAT-PEINH.
BAPI_MBEWX-VAL_AREA = INT_MAT-WERKS.
BAPI_MBEWX-VAL_CLASS = 'X'.
BAPI_MBEWX-PRICE_CTRL = 'X'.
BAPI_MBEWX-MOVING_PR = 'X'.
BAPI_MBEWX-STD_PRICE = 'X'.
BAPI_MBEWX-PRICE_UNIT = 'X'.
************for testing purpose
*wa_valuepart = wa_bapi_te_mara.
*d_extin-structure = 'BAPI_TE_MARA'.
*d_extin-valuepart1 = wa_valuepart(240).
*d_extin-valuepart2 = wa_valuepart+240(240).
*d_extin-valuepart3 = wa_valuepart+480(240).
*d_extin-valuepart4 = wa_valuepart+720(240).
*wa_valuepartx = wa_bapi_te_marax.
*d_extinx-structure = 'BAPI_TE_MARAX'.
*d_extinx-valuepart1 = wa_valuepartx(240).
*d_extinx-valuepart2 = wa_valuepartx+240(240).
*d_extinx-valuepart3 = wa_valuepartx+480(240).
*d_extinx-valuepart4 = wa_valuepartx+720(240).
*append d_extin to t_extin.
*append d_extinx to t_extinx.
remove up to here only.
*WRITE:/ BAPI_HEAD, BAPI_MARC1.
call function 'BAPI_MATERIAL_SAVEDATA'
EXPORTING
HEADDATA = BAPI_HEAD
CLIENTDATA = BAPI_MARA1
CLIENTDATAX = BAPI_MARAX
PLANTDATA = BAPI_MARC1
PLANTDATAX = BAPI_MARCX
STORAGELOCATIONDATA = BAPI_MARD1
STORAGELOCATIONDATAX = BAPI_MARDX
VALUATIONDATA = BAPI_MBEW1
VALUATIONDATAX = BAPI_MBEWX
IMPORTING
RETURN = BAPI_RETURN
TABLES
MATERIALDESCRIPTION = INT_MAKT.
extensionin = t_extin
extensioninx = t_extinx.
IF BAPI_RETURN-TYPE = 'S' .
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = ''.
ENDIF.
IF BAPI_RETURN-TYPE = 'E'.
WRITE:/ 'Error Message ', BAPI_RETURN-NUMBER,
BAPI_RETURN-MESSAGE.
ENDIF.
ENDLOOP.
ENDFORM. "UPDATE_MM
please give me reply
PrashanthWe have encountered the same problem at our company, and the following thread help us to resolve our problem:
Thanks to KevinCur.
Error while saving a .PDF File to a mapped drive
"It has to do with Protected Mode being turned on. I don't know if it was off by default & now it is on with the update but turning it off changes Adobe Reader's behavior back to what the users expect - a prompt warning you if you want to overwrite the existing file & then selecting Yes to overwrite.
To disable Protected Mode:
Start Adobe Reader
Edit - Preferences - Security (Enhanced)
Uncheck Enable Protected Mode at Startup
Close Preferences & Close Reader"
We unchecked the "Enable Protected Mode at startup" box --> Yes --> OK. Our users are happy now. ^_^ -
MM17 Mass Update Tool for Material Master.
Hi Gurus,
We have an appended material master field which was earlier added to the material master.
Now we want to add it as an update field into MM17 Mass Update Tool. But don't know how to do it. Please help.
Thanks in advance.Hi ,
We are not still able to add that field as 'material updation field' in the field pool. Yes it is a Z field, and the concerned table name is MARC.
The SAP version is 4.6 C. We tried to find SAP Note and found one 576160. But it may not work. Could you please advice further ?
We want to add that field into the field pool which appears on clicking the "Select fields" tab. -
Error while cancelling GR material is at Block stock
Hi,
I have created a GR for material QM view is maintain , after GR material updated from QM it is rejected, then we have transfer it in Blocked stock in QA11 now we want to cancel the GR, but while GR cancel with MBST or MIGO the stock type it is shoing as X i.e quality stock now in quality stock is 0 because material is at blocked stock. so while cancelling it is giving error as Deficit of SL Stck.in qual.insp 5,000 NO : 928 MS10 S101
how to solve this,
regards,
zafarHi
you have to move the stock first quality only. once you got the stock in quality you can send the material to vendor with (122) movement type.
For your reference:
1. SAP NOTE 175842 needs to be implemeted first.
2. User Exit QEVA0008 needs to be activated.
3. Then First of all reverse the UD by transaction QA12, by clicking the Customer Function Tab.
4. Now the stock can be reversed for the same Lot by running program RQEVAC50 in SE38.
above procedure you have to do must if amterial belongs to quality.
laxman -
Error in stock updation ( T.code mb1c)
Hi all,
While i'm updating stock using mb1c transaction code the following error apearing.
"Control indicators for controlling area bp01 do not exit"
Please provide solution for this as early as possible.
Thanks & warm regards
kesavHi ramesh,
Thank you for your reply, i sort it out my problem with your suggestion, but i'm getting another error like " account determination not defined for bp01 bpx". For this i did assingment of valuation area , company code and charts of account , still i'm getting above mentioned error.
Please provide solution for above error. If it is possible please provide entire process for material updation(configuration steps).
Thanks and regards
Kesav -
Changing classifications of material master data and reporting
Hello experts,
I have to update long list of material's classifications, I know about the transaction CL24N but in this
one, I have to assign a material to the class and then for each material update the value of the wanted
parameter.
My questions are :
1. Is there any better way to do this massive update ?
2. Is there any standart report on classifications values for all materials ?
Kind Regards,
Amit BerkuHi Amit,
You can look for the Report RCCLBI03 (this Report loads the File). This is the fastest way to load classifications.
You can also use BAPI 'BAPI_OBJCL_CREATE' or write a batch input program, but my advice would be go to for Standard Report if this does not solve your problem then use BAPI and the third option would be to use Batch Input program.
Hope this helps you!
Reetesh -
Material Ledger Functionality with Non Valuated Sales Order Stock
We are in the process of setting up Make To Order (MTO) with Non Valuated Sales Order Stock. We currently use the Material Ledger in our other businesses that use Process Orders.
Does the Material Ledger functionality support MTO with Non Valuated Sales Order Stock? I have been testing this and have not yet figured out how to get ML postings. We are using production orders that settle to sales orders. We do not bring this into inventory, the costs reside on the sales order.
If this functionality does exist, I would assume I need to configure the Material Update Structure but I cannot find any documentation on this.
Any help would be appreciated.
Regards,
GregHi Greg,
no, material ledger will not be able to calculate and allocate actual costs for the sales order in the scenario you describe. It would of course, if you used the valuated sales order stock.
Generally SAP sees in the valuated sales order stocks (avaliable since 3,1 or something) a great improvement and no real reason to use still the non-valuated scenario.
best regards,
Udo -
Serial Number not updating in the system
Hi Frnds
My client is in to retail and has most of the materials under variant configuration. The materials are sold with serial numbers so that they can be tracked and returns/maintenance can be accounted for. The customer is also given discount if he buys that material again using the serial number as reference and the dependency written for that material updates the old purchase qty(old factor) when new purchase qty(new factor) is added to it.
Since the serial number can only be referenced once the goods has been posted and billing has been done. The factors get updated in the system, the factors were updating correctly for the past 2+yrs but since the last couple of months the updating of serial number old factor is screwed. It is not updating for some serial numbers.
Any bright ideas what may be the issue. I have searched every nook and corner but could not trace the cause. Is it possible that a particular serial number can update for a certain number or memory or something???Sorry, but the problem is not solved: it shows the same, 10 numbers and three points.
Seeing the espana2004 message, maybe it is related to the use of a proportional font? All the characters in my Pre's serial number are wide.
This number is needed to download WebOS Doctor. I've had to put my phone in developer mode, connect through novaterm and do a 'lunaprop com.palm.properties.PalmSN' in order to obtain the number. Is there an easier way to get it?
Regards. -
MM - updating Valuation Type in PO History
Hi,
I have a problem during updating the PO History, related with Valuation Type.
The process detailed below:
1-Create PO (ME21N)
2-Inbound Delivery (VL31N)
3-MIGO in Blocked Stock (Mov. Type 103)
4-MIGO for Release Blocked Stock 105
But the problem is for some materials, the Valuation Type in the PO History is update and for other materials it is not updated. I compared both materials and are identical.
Pls. somebody could give me some explanation?
Thank you.Thank you, but I checked both material in the material master accounting view, both material are identical.
When I release blocked stock (103 to 105) one material update the valuation type in PO history at item detail and the other it is not updated.
I can understand, because both material are identical.
Regards.
Maybe you are looking for
-
Movie playback lags SMPTE counter, self-corrects when advance by frame
Recently playback of my QT movies has begun to lag the SMPTE counter by about 15 frames. At any given point when playback is stopped, the timecode burn in the QT reads appx 15 frame behind the SMPTE counter. Curiously, when I advance by 1 frame (usin
-
ITunes can't read iPod contents after Archive & Install
Hi, I recently had to replace the hard drive in my Mac Mini, and now that it is back up and running again iTunes will no longer sync with my iPod. When I start iTunes, I get the following error message: iTunes cannot read the contents of the iPod "Ti
-
What is the process flow in MRP - MD61+MD01,MD02+MD04+COR7
Hi experts, I need one clarification for Material requirment planning ( MRP - Process industries ) My company is newly implemented in SAP so i want some clarification in MRP side. My company flow is 3 rd level converted of FG. 1 st level - Raw paint
-
How to post goods issue as well as billing document during the same time
Hi I have question about SD process , First step is PGI ( Dr. Cost Cr. FG ) >> 1 FI DOC Next Post Billing ( Dr AR Cr. Revenue) >> 1 FI Doc Current process has problem with different posting date between PGI and Billing doc .At my company i
-
Solaris 2.6 - System Call faults
Hi Sun Forums. Machine Description : SunOS serv-sif 5.6 Generic_105181-28 sun4u sparc SUNW,Ultra-Enterprise Number of CPU's : 4 (400Mhz) Physical Memory : 5120 Mb Top Output : PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND 11115 syb119 2 1