IDOC - MATERIAL CHANGES

Hi All,
There are two SAP Boxes for us..One is used for Purchasing and Inventory activites and other Box is used for Warehouse Management activites.
When I change a material in details in purchasing box....IDOCs Will be created and moved to Warehouse Management Box....
As soon as I change tha material, is there a way where I can see the IDOC generated when I change the material details...Like I want to see the IDOC number and the material name at one place.......
I knew you can view through WE02.....But I want to know if there is another way of viewing IDOC generatred by changing material and Material number at one place....

Hi
You can do that in WE02 itself, select the Idocs to be listed and execute
Select the MATMAS Node and click the button 'List Specific segment', you will get the Idoc and material number at one place.
It will ask for segment name when u click the button, it can be given as 'e1maram'.
Regards
Sandy
Edited by: Snehalkumar Kadam on Feb 24, 2009 3:47 PM

Similar Messages

Idoc for Material Change

Hi Experts,
The requirement is to receive a standard Idoc for material change and trigger the material creation process in case the material does not exist.
Secondly, what is the Idoc for material change?
Thanks and Regards,
Ravi

Hi,
Go through the following Steps for Creating IDoc Via ALE
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error.
hope this helps you.
plz reward if useful.
thanks,
dhanashri.

FM to fill outbound IDOC with change document details.

Hi ,
I am working on an enhancement EXIT_SAPLMGMU_001 for an interface to track the changes to the material master.
Can someone please let me know if there is a FM to populate outbound IDOC with change document details like when a material is
created /changed. Thanks much.
Regards,
Sanjeev
Edited by: sanjeev.s on Apr 14, 2010 3:32 PM

Call the function module "MASTER_IDOC_DISTRIBUTE" to create idoc. Use function module "CHANGEDOCUMENT_READ_HEADERS" to get the change document details.
Regards
Vinod

ALE distribution of planned material changes made using MM12

Greetings,
I have searched and come up empty-handed looking for an answer, perhaps someone in this forum can point me in the right direction. I am trying to find out if there is a tcode and idoc message type that will distribute a planned material change, prior to it's activation, while it is still in it's planned state. While in the source system, I can see these changes in mm14, I do not see the "future" values as part of the MATMAS generated by a BD10, nor as part of the ECMMAS generated by a CC92 transaction. Ideally we could allow material master changes in our source system on a future date using the same ECM number as a BOM change for example, and distribute these changes together to the target system, prior to the ECM effectivity, without further requiring a additional BD10 to be performed after the material change activation date. Does anyone have advice on this? Thank you for any info you can provide.

1. Activate change pointers
2. Customize it to check for status before activation and trigger the distribution. (I think it should generate even if the material is not activated so no customization required - but just test and confirm. It's been a while I've looked at this).
3. Maintain this in your distribution model and distribute master data accordingly.

Inbound EDI/Idoc to change PO

Hello Dear Sappers,
I'm using message type ORDRSP (Idoc ORDERS05) for inbound Vendor confirmation, and it works.
Our Vendors also send price changes, quantity changes, material changes and cancellation to PO item.
Can i use ORDRSP to update my PO item? Or do i have to use a seperate message type? (PURCHG?? ORDCHG??) or a different IDOC alltogether?
Thanks in advance,
Daniel

you can use ORDERS05, we are also using ORDERS04 with out our Z extension.
and we create PO with msg type PORDCR02 with out z extension

ALE IDOC - Material Master

Hi,
I have triggered Idocs for material master changes.
For some materials, the material description is blank in idocs,however; we have the material description data in SAP.
I have checked the changes in material master, the changes made for material description also on the respective date.
Plesae let me know the cause of sending the material changed record with the description as blank.
Please consider it as a priority basis and help me.
Regards,
Usha.
Edited by: Usha Rani Achana on Apr 22, 2010 10:18 AM

>
Usha Rani Achana wrote:
> Hi,
>
> I have triggered Idocs for material master changes.
> For some materials, the material description is blank in idocs,however; we have the material description data in SAP.
>
> I have checked the changes in material master, the changes made for material description also on the respective date.
>
> Plesae let me know the cause of sending the material changed record with the description as blank.
>
> Please consider it as a priority basis and help me.
>
>
> Regards,
> Usha.
>
> Edited by: Usha Rani Achana on Apr 22, 2010 10:18 AM
I have loaded hundredthousands of materials via ALE method and never experienced a loss of material description.
If that would be the case, and you really just using the SAP standard, then you should open a message at SAP.
MAybe you implemented OSS Note 1364357 - Defined language for material master transfer
and then restricted the transfer to a certain language only.

NEED ALE IDOC MATERIAL

PLZ CAN ANYBODY SEND ME GOOD MATERIAL ON ALE IDOCS
PLZ NO LINKS
I HAVE THE LINKS I JUST NEED GOOD PPTS STEP BY STEP
POINTS ASSURED FOR GOOD MATERIAL
MY MAIL ID is [email protected]

Refer this material..
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
You can directly create an iDoc using some transaction like...
Use TCODE bd10 - to Send Data
and TCODE bd11 - to Get Data
and you can check the IDoc List using TCODE we02.
As you want step by step procedure.
1. Define Logical System and Assign Logical System
TCODE sale
2. Define RFC
TCODE sm59
3. Define Port
TCODE we21
4. Define Partner Profile
TCODE we20
5. Define Distribution Model
TCODE bd64
6. Send Data
TCODE bd10
7. Get Data
TCODE bd11
8. IDoc List
TCODE we02
There are basically two types of IDOCs.
Basic IDOCs
Extended IDOCs
Idoc Components
Basic Idoc
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extension Idoc
Extending the functionality by adding more segments to existing Basic IDOCs.
Creation of IDoc
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Create IDOC Type
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
u can also check all these links related to idocs
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sap-img.com/
http://www.sappoint.com/abap.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
Reward if it is usful,

How to differentaite between material created on & material changed ??

Hi all,
How to differentiate between material created and material changed???
is there any flag or indicator present to differetiate between two....please guide me.
Thanks,
Ashu

Hi Ashu,
I just want to clarify one point from you.
i always prefer to hit MARA with below feilds, if you want track singe change of the material
ERSDA - Creation date
ERNAM - Name of Person who Created the Object
LAEDA - Date of Last Change
AENAM - Name of person who changed object.
some times material may change multiple times, in these cases we need to hit CDPOS and CDHDR
to track the material changes....
or you can create a custom table with the feild time & date of change...and when ever material getting changed
in the ME21n exit update one entry in custom table.
Many Thanks
Raghu

Regarding display of material changes- really urgent

hi,
i had assigned a work in which i have to collect information that in the period from 1.12.2007 to 31.12.2007 the number of materials had been changed and what changes had been made to them.
plzz tell me about it as help will be definately rewarded.

Hi,
PAss cdhdr-objectclas = MATERIAL
cdhdr-udate = sel. screen value
get all changenr from cdhdr
pass all to the cdpos-changenr & objectclas = MATERIAL
from cdpos-chngind = 'U' means material changed
and if chngind eq 'I' means material entry created.
else, MSTA is already there to just know which mat. created pass ersda value
and for changed pass laeda value.
Reward points for the helpful answer....
Regards,
Brijesh Patel

IDOC for changing user status to 'HIST' on Functional Location

Hi.
Can anyone please support me with an inbound IDOC for changing status on existing Functional Location?
Thanks.

Hi ,
I am not sure whether it would work with LSMW but if your on ECC 6.00 ,Enhacement Pack 3 then you have BADIs which allow you to make collective status changes in IW38 .The below are those BADIs :-
BADI_EAM_RIAUFK20_FCODE_CUS1 :Implement Customer Function Code in Order List
BADI_EAM_RIAUFK20_FCODE_SAP1 :Implement SAP Function Code in Order List
Else if your on lower version then write up a batch programme which checks the PM Order types with specific status and sets user status using FM STATUS_CHANGE_EXTERN[This is used to set or delete User Status] in SE37 ..
regrds
pushpa

Workflow for material changed

Hi Gurus,
I would like to implement a workflow with a mail which wil be triggered whenever a material is changed.
I have created a workflow using SWDD..How can I link this workflow to Material change transaction(MM02)..
I am new to this workflow...Pls help me...
Thanks in advance...
Regards,
Saj

Hi,
you need to create an event for your change document BOR 1001006 thru SWEC.
create a similar event in your BOR Event and use this event in the Basic Data of your WF.
So whenever a material is changed your event would trigger your WF.
Hope I am clear,
any issues reply back to this thread.
Aditya.
P.S
just a suggestion, could you put in your name instead F1 (as I like referring to names, though I just address all by initials) offcourse no hard n fast rule,
but since its a <b>wonderful Forum</b>, lets know each other .
Well my friend I still have no issues with your Display Name, it was just a thought.

Material changes checking

Hi all,
How to check material changes from last year to current year in material master level

Hi,
You can check it in the Change or display mode of Material master MM02 / MM03 it self or by transaction MM04.
In MM02 / MM03 transaction, click on the 'Environment' tab from menu bar then select Display changes. A pop up will be displayed with the list of all changes for that material in the system. Select the required line and click on the details (F2). Complete changes will be displayed.
Regards,
Hiren Ramani

Reg: Material change Management.

Dear Friends,
can i get some information about Material change management.
Please let me know..
thanks in advance.

Hi,
Pl go through the sap help... will get deatail idea.
[http://help.sap.com/erp2005_ehp_04/helpdata/en/d8/731cab4b7511d1894b0000e8323c4f/frameset.htm]

Table stores the history of material change

Hi, expert,
please kindly tell me which table stores the history of material change(MM04 is inconvenient).
Regards,
David

I think your requirement availble in this table
T005T      Country Names
T134T      Material Type Descriptions
T606R      Legal Control: Legal Regulation Descriptions
T685T      Conditions: Types: Texts
TCURM      Customizing: MM Configuration
TSKMT      Taxes: Materials: Texts
by
prasad

IDOC after Material Change

Hi all,
I would like to send a IDOC after a material has changed.
I have to send the complete material by IDOC, so not by the change pointers (TC BD21).
Normally a user would change a material and then would start BD10 to send the material.
I have found a user exit EXIT_SAPLMGMU_001 but a that point the material is not saved.
How can I start BD10 after the material has been saved?
Or does someone know another way to achieve this?
Greetings Fred.

Hi Frek ,
If u r working ECC after saving the material (Please Check the code) . After this code create an Enhance Spot . where u can call ur transaction .
I hope it resolves ur problem .
Rgds
Sree M
Edited by: Sree Merugu on Apr 21, 2008 5:00 PM

IDOC - MATERIAL CHANGES

Similar Messages

Maybe you are looking for