IDOC for Batch Master Conversion

Hi,
Is there any IDOC for Batch Master Conversion (Transaction : MSC2N) ?
The data being maintained is in Basic data 1 and classification tabs.
Regards,
Esha Raj

Hello,
I faced the problem with BATMAS03. When drilling down to F'tn BAPI_BATCH_SAVE_REPLICA I could that one and similar BATMAS03 get to work with filling following set of fields. Adapt of course the values to you're system.
BAPIBATCH_SAVE_REPLICA_
MATERIAL = 000000000000033001
BATCH = 12543872
PLANT = D010
CLASSALLOCATIONS
CLASS_TYPE 023
OBJECTKEY 00000000000003300112543872 (in our case MATNR&BATCH combination, dependend on system setting Plant could also be needed)
CLASSNUM FROZEN_FINISHED (Classification Class)
OBJECTTABLE MCH1
CLASSVALUATIONSCHAR
CLASS_TYPE 023
OBJECTKEY 00000000000003300112543872
OBJECTTABLE MCH1
CHARACT LOBM_ZUSTD
VALUE_CHAR X
This works now fine and similar for the BATMAS IDOC
Hope this is helpfull for you.
Dirk

Similar Messages

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.

I want IDOC for Vendor master updation ( XK01 &XK02 )

Hi
I want to do LSMW in IDOC method for this vendor updation.
So I want IDOC for Vendor master updation ( XK01 & XK02 ).
I want to do both create vendor and change also.
Regards,
Ravi
Edited by: kandukuri ravi on Dec 1, 2008 2:56 PM

Hi,
For Vendor Master using IDoc's for LSMW,Use Message Type = CREMAS and Basic Type = CREMAS05.
For Basic type 01,02,03...05 are versions which includes more fields in basic type so better use latest version.
Hope it will help you.
Regards,
Sudhakar Reddy.A

Generate outbound idoc for Customer Master

Hi Developers,
I have requirement to generate outbound IDOC for Customer Master Data. I need to send customer master data through an Outbound IDOC. Can we generate an outbound DEBMAS06 idoc? Can someone help me finding a solution to this problem?
Thanks in advance for helping.
Regards,
Gajendra

Hi,
If you have done all the required settings (logical system, partner profiles, distribution model), then either transaction BD10 / BD14 will help you generate the IDOC.
If you want to send the idocs automatically, then you will to configure some program.
Unlike transaction data, Master data IDOCS are not triggered immediately, you will have to do the required configuration in SPRO.
Transaction SPRO
SAP Customizing Implementation Guide -->
SAP Web application Server --> Application Link Enabling --> Modeling and Implementing Business Processes -->
Master Data distribution --> Replication of Modified Data --> Creating IDOCS from Change Pointers
Take a look at this thread.
Re: automatic Idoc outbound
Regards,
Ravi
Note : Please mark the helpful answers
Message was edited by: Ravikumar Allampallam

Outbound IDOC for Article Master in WPMA without Price

Hi,
How to Generate an Outbound IDOC for Article Master in WPMA Tcode without maintaing Price for the Article. Please suggest Is it Possible in IS-Retail. If so, what needs to be Done.
Regards,
Selvakumar. M

Hi Selvan
In patner profile of outbound, Assign WP_PLU01 instead WP_PLU03..
This will solve ur problem
Regards
Vijai Jain

About the effect for batch level conversion from material to plant level

Dears,
Now we use batch management at material level in our system, now we want to change to batch level from material level to plant level, what effects or risks it will bring during the process of conversion?
Thanks a lot
Zhongkai

Hi
check the following SAP help link it is very helpful:
http://help.sap.com/saphelp_40b/helpdata/es/d2/1d4b6e5733d1118b3f0060b03ca329/content.htm
at the link you can find the following
Specify batch level and activate status management
In this IMG activity, you specify the following:
the level at which batch numbers are unique
whether batch status management is active in the client
the plants in which batch status management is active
the initial status of new batches
Batch level
Batch numbers can be unique at the following levels:
at plant level
at material level
at client level for a material
If you choose plant level, the batch number is unique in conjunction with the respective material and the plant. If you choose material level, the batch number is unique together with the material. At client level, the batch number is unique in the whole client.
To change the batch level, you have to start a conversion program. This program first checks whether conversion is possible and outputs an error log containing all batch numbers that occur more than once at the new level. Now you need to manually transfer these batch records to numbers within Inventory Management using a transfer posting 'material to material'.
If you change the level from plant level to a higher level, it is possible that batches with the same batch numbers in different plants are actually identical. In this case, all you have to do is remove stocks (including previous period stocks) so that all batches with the same batch numbers, except one, can be reorganized.
When you convert from plant level to material level, the material is then to be handled in batches in all plants in which it is defined.
Standard settings
In the standard R/3 System, batches are unique at plant level.
Activities
To change the batch level, proceed as follows:
      1. Choose the level at which you want your batches to be unique.
      2. Save the new settings and choose Back.
      3. Select function Batch level -> Conversion.
      4. If necessary, carry out the conversion in test mode first.
Further notes
Note that you cannot reset conversion from plant level to a higher level in the standard.
If you create a client by copying an existing client, initially, there are no settings in the target client at batch level. The system makes the settings in the target client only when you have carried out an activity (maintaining master data or posting a goods movement, for example).
SETTINGS BEFORE/AFTER CLIENT COPY:
Source client Target client
Client level Material level
Material level Material level
Plant level Plant level
Batch status management
Batch status management is an additional function provided by the standard R/3 System.
Standard settings
Batch status management is not active in the standard R/3 system.
Activities
To activate batch status management, proceed as follows:
      1. Choose Batch status management active.
      2. Save the new setting and choose Back.
      3. Choose Batch status management -> conversion.
      4. If necessary, carry out the conversion in test mode first.
Further notes
Batch status management is linked to the batch level. At material and at plant level, the status management settings are valid within the client, that is for all plants. However, if you have defined batches to be unique at plant level, you have to select the plants in which status management is to be active using function Plants with status management.
If you activate status management, all existing batches are assigned status 'unrestricted'. If you deactivate status management, the systems transfers all restricted batches to unrestricted stock within conversion. Restricted stock only exists if status management is active.
If you create a client by copying an existing client, status management is automatically activated if batches exist in the target client, independent of the settings in the source client. If no batches exist in the target client, it is not activated. In this case, you have to activate or deactivate status management manually, if required.
Plants with batch status management
Activities
To select the plants in which status management is to be active, proceed as follows:
      1. Set characteristic Batch status management for those plants in which batch status management is to be active.
      2. Save your settings and choose function Back.
      3. Choose function Batch status management -> conversion
      4. If necessary, carry out the conversion in test mode first.
Initial status of a new batch
Using this function, you can specify for each material type which initial status new batches are to be assigned. However, if you use a quality management system, this specifies the status of the batches.
Hope it will help
Best Regards

Authorization control for batch master

Hello Experts,
I have a special requirement from client on authorization control on batch master. The requirement is user should not be allowed to change the batch header details but allow to change selected characteristic values. For e.g If I have a batch A, the header values such as prod date, country of orgin etc should not be allowed to change. In classification view few characteristics only should be editable, rest all should only be displayed.
Is there any option to do this. Either through authorization control or exits. We dont want to create a custom transaction to achieve this.
Thanks in advance
Prathib

Hello
The following document explains how to check which authorization objects are called on each transaction:
How to analyze authorization issues in debug
BR
Caetano

IDOC for Equipment master

Hi,
I am new to IDOC concept and need to transfer Equipment master from a SAP system to non SAP system.
please let me know the following:
1. Is there any standard message type and Idoc type available
    for Equipment master ?? ( For example we have
    MATMAS05 for material master)
2. Is there any standard transation available for equipment
    trasfer???( For example BD10 for sending material)
3. Is change pointer facility available for equipment master??
    If yes please provide me the details
Thanks

Hi Preethi
Please use LSMW in loading euipment master using the Basic type EQUIPMENT_CREATE01 and assign the source legacy file.You can use the message type EQUIPMENT_CHANGE01 to change it.See in WE02 BD87 the stus whether it has been posted or not.
           Since your data would be going to non sap that means you have to create partner profile for outbound processing and also activate the port(WE21) for outbound processing.
                 If your client is intilligent enoough and also big than if it has an ETL tool than extraction from spreadsheet in the form of idoc would be much easier and would cut short the time consumed in writing large programs .However the business needs to have an existing legacy system and you try to convert data .
      Please do revert back incase of any issues.
Regards
Somnath

Regarding ALE-iDoc for Customer Master, J1ID and FD32

Hello all
Scenario:
As per client's requirement we have to develop idoc so that followings requirements will meet:
Say there are two servers a) MDM Server b) PRD Server
1] As and when I'll create customer master data in MDM server then customer master should get created with that data in PRD server
which I can achieve through BD12 by doing some idoc enhancements
2] Simillarly when i'll create data using transaction J1ID and FD32 in MDM Server (Data relevant to customer master) then that data also should get created in PRD server using Idoc
May I know which
1)message type we can use (as we use DEBMAS in case of Customer Master) for J1ID and FD32
2) Any transaction to send data from one server to another server for transaction J1ID and FD32 (as we use BD12 in case of Customer master for sending data created using transaction XD01)
Thanks,
Mahesh

Hello Mahesh,
In the case of customer master it would be better if you would use standard message types and t code to transfer ddata.
But in the case J1ID and FD32 you can build a standalone idoc
Follow these steps to build custom message types and futher transactions
WE81 - Create message type
WE31 - Create segment
WE30 - Create Idoc type
SALE - Define Logical system (not required if already exists)
SM59 - Define RFC (not required if already exists)
WE21 - Define ports (both in sender and receiver)
WE20 - Define Partner profile (both in sender and receiver)
BD46 - Distribue the model view.
SE38 - Create a program to send the idoc in the sender sytem.
SE37 - Build inbound function module to receive the idoc for receiver system
WE57 - Assign FM to message type
BD51 - to change the characteristics for inbound FM
WE42 - Create Inbound process code.
Hope this would help you.
Thanks and Regards,
Ranjith Nambiar

Idoc for plant master

Hi Everyone,
This is my first project on ALE/Idocs ... I need to send the Plant information using Idoc but I'm not getting any Idoc to send the information. So do I have to create a custom Idoc for this??? The feilds whhich I need to send are WERKS,NAME1 and ORT01.

Hi this will help u.
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.
>>>> SAP ALE & IDOC<<<<
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.
with regards,
Hema Sundara.
pls reward if it is helpful.

Outbound IDOC for customer master

Hi
I want to configure that as soon as I create a customer master using the transaction XD01 it should generate an outbound IDOC. Can anyone tell me how to configure this and what need to be br configured.
Thanx in advance
regards
Vinod

Hi Vinod,
We can distribute master data in many ways like Send original copy, Send changes and third one is Pull master data.
Go to txn SALE, and follow the steps to configure your scenario.
I think in your case you have to use Message Control or
Output Determination.
visit this link for message control...
http://help.sap.com/saphelp_erp2004/helpdata/en/c8/198afa43b111d1896f0000e8322d00/frameset.htm
Regards,
Narinder Hartala

Idoc for Material Master Specific to SAP AFS

Hi All,
I have requirement to create & extend the material master from Non-SAP to SAP specific to AFS industry, however can anyone suggest which inbound idoc needs to be configured in details like (Message type, basic type & process code)
Also please suggest how it can be extend at the same time to different plants
Thanks & Regards
Parag

Hi Tomek,
Thanks for details, can you please guide / suggest on extend the mateial for other plants & Storage location as well after creation of material.
Thanks
Parag

Classification Segment in IDOC for Material Master

Hi,
Can anyone let me know which IDOC message type will get me the classification segment in that. I am assuming that to be the segment is E10CLFM but i dont know which IDOC message type has it.
which IDOC type will get the batch data Inbound to SAP with all the batch class and batch characteristics to be posted to inventory.
thanks a bunch

you can create inventory with IDOC
message type MBGMCR
basis type MBGMCR03
alternative with program RM07MMBL
You have to decide if you create batches internally while loading inventory or if you load the batches seperatly and assign just the batch number when doing the movement for initial inventory.
Especially if your batch characteristics cannot be valuated automatically, you have to load them before inventory to get all the characteristic values.
batches can be loaded with Idoc
BATMAS
BATMAS03

Enhancement for batch master (BATMAS03)

Hi,
I've found an extended IDoc ZBATMAS03 (basic type: BATMAS03). It's being used for generating outbound IDOc usiong change pointers. A new segment Z1BATMAS has been added to the extended one.
Now I'm not able to find where this segment is being populated.
I tried searching in FM: MASTERIDOC_CREATE_SMD_BATMAS and the where used list for the new segment.
can anyone tell me how to find where the above new segment is being populated?
regards,
Ravi
Moderator message - Cross post locked
Edited by: Rob Burbank on Oct 22, 2009 11:31 AM

Hi,
I've found an extended IDoc ZBATMAS03 (basic type: BATMAS03). It's being used for generating outbound IDOc usiong change pointers. A new segment Z1BATMAS has been added to the extended one.
Now I'm not able to find where this segment is being populated.
I tried searching in FM: MASTERIDOC_CREATE_SMD_BATMAS and the where used list for the new segment.
can anyone tell me how to find where the above new segment is being populated?
regards,
Ravi
Moderator message - Cross post locked
Edited by: Rob Burbank on Oct 22, 2009 11:31 AM

OutBound IDoc for Material master

Hi everyone
I need to send Material Masterdata whenever data is saved in MM01,MM02 using BTE1250 .
I need to use function module MASTERIDOC_CREATE_REQ_MATMAS to send idoc.
Can anyone please help me with a basic program/ code for sending Idoc using MASTERIDOC_CREATE_REQ_MATMAS.
I am new to Idoc and could not understand programs given in SDN.
Thanks in advance.

Hi,
Refer to SAP standard program "RBDSEMAT".
Regards
Vinod

IDOC for Batch Master Conversion

Similar Messages

Maybe you are looking for