ALE:Material Master Data Distribution

Hi
I am new to ALE Material Master Data Distribution and if the questions are incorrectly worded, please accept my apologies. It is due to lack of knowledge.
I am doing Material Master Data distribution and I am using standard basic type MATMAS03. The standard TCode MM01, MM02 has SAP tables and 3 custom tables.
I have turned the active on using BD61 and change pointers to message type.
Q: Is the change pointer, applicable to entire material master? i.e. if I change a field in Z table or standard material tables, can an IDOC be created for the entire material record?
Q: What is the function of BD52? Does this override the option Activate Change pointers for message type? Does it mean, if the changes are made to those fields in BD52 a change pointer is created?
Q: If I change Z table only, will there be a change pointer created? If not, how could I accomplish this using BD52.
Q When do we use the enhancement MGV00001?
Also, If you could add anything in addition to above queries, it will be helpful to me and I appreciate it.
With regards,
William

Thank you Sudhakar.
Your tips are good, but, I was not able to get the problem resolved.
Let me explain what I have done based on your tips.
1. MATMAS uses MATMAS03. The basic type has NOT been modified to have z fields yet.
2. Using BD52, i have created the following fields
MATERIAL ZEMM_MARA_TECH IM_ADVISORY_CODE
MATERIAL ZEMM_MARA_TECH KEY.
3. Modified the MMR for IM_ADVISORY_CODE.
I did not see a change pointer for this change.
Q: When I created above entry using BD52, was asking the table name. The table name is stored in TCD0B. What TCode is available the entries in TCDOB. For the time being, i created using SQL.
Q. Is there a follow up configuration required to capture the changes?
I will award the points in a couple of days time, even if I do not get the solution, because you have spent your precious time for the community. I will wait for a couple of days for other suggestions and close the Problem.

Similar Messages

Material Master data distribution using the Classifications

Hi All,
I am attempting to cater for a business scenario where we wish to distribute material master records via IDOCS by assigning a class to each material we wish to send out.
We have a new classtype (Z01) which is setup for distribution purposes (the status for this class type has been maintained). I have defined a filter using classes in BD60.
The next step was to setup the distribution model for my message type and partner. I added the filter group in the distribution model for the message type (filter group "dependant on class membership"). The final step after generating the partner profile was to assign a new class that I created to the material master.
We are using change pointers and BD21 to create the IDOCs. I am managing to create the outbound IDOC but I am getting a 29 Status with an error message "Class type Z01 , receiving system ZFR001 : no list maintained". ZFR001 is the name of the external partner. The name of the class that has been assigned to the material master is also ZFR001. There are no characteristics assigned to the class.
Has anyone setup a similar scenario? I'd appreciate any guidance as I have hit a bit of a wall.
Best regards,
James.

Hi,
The message type to send HR data is HRMD_A, i don't think that filtering this only message you achieve what you describe.
In this message type, yo can define filters to send only the relevant infotypes that you need, but all of them will be send in the same idoc, for one employee.
So I think to achieve what you want, you should create customer Message types (Z's) as reductions of HRMD_A standard message type and then in BD64 create one different Model for each one. So in each model you can put only the infotypes you want. You should very carefull with the updating in your destination system, because if you process all the message type at the same time, there will be a lot of blocking in employee objects.
It is weird what you want to do, but this could be the solution.
Regards,

Full Master Data Distribution in ALE - Vendor Master CREMAS(Full Distributi

Hi Experts,
   I have to do a Full Master Data Distribution in ALE - Vendor Master CREMAS(Full Distribution) using BD21.
   I have already read the blog of Mickel and incorporated the code in Change_Pointer_Read.
   It is still not working. Should I include the code at the end of the Function Module. If yes, how to code at the last as
   I can include my code at the SAP suggest Enhancement and End Enhancement.
   Is there any way I can create the implicit Enhancement at the end of the Function Module.
   I will appreciate any help to make the Full Distribution work.
Thanks,
Mich

Hi,
   Here is the link.
   /people/michal.krawczyk2/blog/2009/06/04/distribution-of-full-master-data-objects-from-change-pointers
   My requirement is to send the whole Vendor Master in a IDoc even though for eg there is only one field change in address field of Vendor Master. Full Master Data distribution. But the program BD21 creates only IDocs with segments where the changes are made in the particular tab like address.
   Is there any Enhancement or way to enforce the whole Master Data(CREMAS) to be distributed.
   I will really appreciate any helpful answer .
Thanks,
Mich

Master Data Distribution !

Hi!
   I want to know the purpose of master data distribution for the following between the vendor & the customer.
   1. Material Master
   2. Vendor Master & Customer Master.
Whats the purpose of linking our system with our vendor or customer etc with <b>regard to master data</b>
Pls explain in detail.
Thanks
Rahul.

Hi Rahul,
We dont do master data distribution with customer system or vendor system.
Master data distribution is done between distributed systems of the same organization using ALE configuration. So we dont link to customer or vendor systems for transfering master data but for transfering transactional data like purchase orders or sales orders etc.
Master Data Distribution
Rather than distributing the complete master data information, views of the master data can be distributed (for example, material sales data, material purchase data). Each view of the master data is stored in a separate message type.
Users can specify which data elements in a master record are to be distributed.
Various distribution strategies are supported:
·        Cross-system master data can be maintained centrally and then distributed. The final values are assigned locally.
·        A view of the master data can be maintained locally. In this case there is always one maintenance system for each view. After the master data has been maintained it is transferred to a central SAP system and distributed from there.
Types of Distribution
·        Active distribution (PUSH)
If the master data is changed (for example, new data, changes or deletions), a master data IDoc is created in the original system and is distributed by class as specified in the distribution model.
·        Requests (PULL)
A request occurs when a client system needs information about master data held in the system. You can select specific information about the master data, for example, the plant data for a material.
If you want to be notified of all subsequent changes to the master data, this has to be set up manually between the two systems. It is not yet possible for this to be done automatically in the distribution mechanism in the original system.
Transferring the Master Data
A distinction is made between transferring the entire master data and transferring only changes to the master data.
If the entire master data is transferred, a master IDoc is created for the object to be distributed in response to a direct request from a system. Only the data that was actually requested is read and then sent. The customer specifies the size of the object to be distributed in a request report.
If only changes are transferred, the master IDoc is created based on the logged changes.
Reward points for the useful answers,
Aleem.

Transfer of material master data with Classification view

Dear Experts
I want to transfer material master data between R/3 using ALE. We are able to send master data using BD10 without classification view.
Please let me know in detail the configuration, steps invloved in sending materail master along with classification view.
Regards
Samal

HAI FRIENDS,
CHANGING CLASSIFICATION VIEW FOR MATERIAL USING BAPI
->CREATE CHARACTERISTIC USING TCODE CT04
->CREATE CLASS USING TCODE CL01 .
-> RUN THIS PROGRAM TO CHANGE THE CLASSIFICATION VIEW
PARAMETERS: P_MATNR TYPE MARA-MATNR. "MATERIAL
DATA: OBJECTKEY TYPE BAPI1003_KEY-OBJECT,
OBJECTTABLE TYPE BAPI1003_KEY-OBJECTTABLE,
CLASSNUM TYPE BAPI1003_KEY-CLASSNUM,
CLASSTYPE TYPE BAPI1003_KEY-CLASSTYPE,
ALLOCVALUESNUMNEW TYPE TABLE OF BAPI1003_ALLOC_VALUES_NUM WITH HEADER LINE,
ALLOCVALUESCHARNEW TYPE TABLE OF BAPI1003_ALLOC_VALUES_CHAR WITH HEADER LINE,
ALLOCVALUESCURRNEW TYPE TABLE OF BAPI1003_ALLOC_VALUES_CURR WITH HEADER LINE,
RETURN TYPE TABLE OF BAPIRET2 WITH HEADER LINE.
OBJECTKEY = P_MATNR.
OBJECTTABLE = 'MARA'.
CLASSNUM = 'MTS_CABLE_BIN1'. "CLASS(CREATED USING CL01)
CLASSTYPE = '023'. "CLASS TYPE (023 FOR BATCH)
CALL FUNCTION 'BAPI_OBJCL_CHANGE'
EXPORTING
OBJECTKEY = OBJECTKEY
OBJECTTABLE = OBJECTTABLE
CLASSNUM = CLASSNUM
CLASSTYPE = CLASSTYPE
STATUS = '1'
STANDARDCLASS =
CHANGENUMBER =
KEYDATE = SY-DATUM
NO_DEFAULT_VALUES = ' '
IMPORTING
CLASSIF_STATUS =
TABLES
ALLOCVALUESNUMNEW = ALLOCVALUESNUMNEW
ALLOCVALUESCHARNEW = ALLOCVALUESCHARNEW
ALLOCVALUESCURRNEW = ALLOCVALUESCURRNEW
RETURN = RETURN
LOOP AT RETURN.
WRITE: / RETURN-TYPE ,RETURN-MESSAGE.
ENDLOOP.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT =
IMPORTING
RETURN =
BY VENKATESWARAREDDY D
MYTEC SOFT LTD

Material Master Data load failed

Hi All,
I am loading material master data. I have around 8055 records in R/3. The load has failed with an error "Non-updated Idocs found in Business Information Warehouse" and asking me to process the IDocs manually. I have checked in WE05 for the IDocs and found 3 Idocs with status 64(IDoc ready to be transferred to application).
But when I checked in the manage screen of the 0MATERIAL I could find the Transfered and Updated records as 8055. I have even checked the data in 0MATERIAL and found that all the data(8055 records) has already been uploaded.
Why is it still showing an error(load failed) even when all the data has been uploaded? What should I do now?
Best Regards,
Nene.

hi Nene/Sankar,
for material text no language please check Note 546346 - Material texts: no selection on languages
and for why idocs problem, check e.g Note 561880 - Requests hang because IDocs are not processed, Note 555229 - IDocs hang in status 64 for tRFC with immediate processing.
hope this helps.
Note 546346 - Material texts: no selection on languages
Summary
Symptom
When loading material texts from R/3 into the Business Information Warehouse, you cannot select languages.
Other terms
DataSource, 0MATERIAL_TEXT, InfoSource, InfoObject, 0MATERIAL, SPRAS, LANGU, 0LANGU, MAT_BW, extraction, selection field, delta extraction, ALE, delta, change pointer
Reason and Prerequisites
As of PI/PI-A 2001_2 Support Package 6, the selection option for the 'SPRAS' field in the OLTP system was undone in the 0MATERIAL_TEXT DataSource. (Refer here to note 505952).
Solution
As of PI/PI-A 2002_1 Support Package 4, the 'SPRAS' field is provided for selection again with the 0MATERIAL_TEXT DataSource in the OLTP system. When loading the material texts from BW, the language is still not provided for selection in the scheduler, instead all languages of the language vector in BW are implicitly requested from the source system. However, during the delta update in the source system, the change pointers for all languages in the source system are now set to processed, regardless of whether the language was requested by BW or not.
Import
Support Package 4 for PI/PI-A 2002_1_31I - PI/PI-A 2002_1_45B
Support Package 4 for PI 2002_1_46B - PI 2002_1_46C
Support Package 3 for PI 2002_1_470
In transaction RSA5, copy the D version of the 0MATERIAL_TEXT DataSource to the A version.
Then replicate the DataSources for 0MATERIAL in the BW system. The 'SPRAS' field is then flagged again as a selection field in the transfer structure of the 0MATERIAL InfoSource. The transfer rules remain unchanged. Activate the transfer rules and perform a delta initialization again.
Note 561880 - Requests hang because IDocs are not processed
Symptom
Data extraction in a BW or SEM BW system from an external OLTP System (such as R/3) or an internal (via DataMart) OLTP System hangs with the 'Yellow' status in the load monitor.
After a timeout, the request status finally switches to 'Red'.
Information IDocs with the status '64' are displayed in the 'Detail' tab.
Other terms
IDoc, tRFC, ALE, status 64
Reason and Prerequisites
Status information on load requests is transferred in the form of IDocs.
IDocs are processed in the BW ALE model using tRFC in online work processes (DIA).
IDoc types for BW (RSINFO, RSRQST, RSSEND) are processed immediately.
If no free online work process is available, the IDocs remain and must then be restarted to transfer the request information.With the conversion to asynchronous processing, it can often happen that no DIA is available for tRFC for a short period of time (see note 535172).
The IDoc status 64 can be caused by other factors such as a rollback in the application updating the IDocs. See the relevant notes.
Furthermore, you can also display these IDocs after the solution mentioned below, however, this is only intended as information.
You must therefore analyze the status text.
Solution
We recommend asynchronous processing for Business Warehouse.
To do this, you need the corrections from note 535172 as well as note 555229 or the relevant Support Packages.
The "BATCHJOB" entry in the TEDEF table mentioned in note 555229 is generated automatically in the BW system when you import Support Package 08 for BW 3.0B (Support Package 2 for 3.1 Content).For other releases and Support Package levels, you must manually implement the entry via transaction SE16.
Depending on the Basis Support Package imported, you may also have to implement the source code corrections from note 555229.
The following basic recommendations apply in avoiding bottlenecks in the dialog processing and checking of IDocs for BW:
1. Make sure there is always sufficient DIA, that is, at least 1 DIA more than all other work processes altogether, for example, 8 DIA for a total of 15 work processes (see also note 74141).
TIP: 2 UPD process are sufficient in BW, BW does not need any UP2.
2. Unprocessed Info IDocs should be processed manually within the request in BW;in the 'Detail' tab, you can start each IDoc again by selecting 'Update manually' (right mouse button).
3. Use BD87 to check the system daily (or whenever a problem arises) for IDocs that have not yet been processed and reactivate if necessary.
However, make sure beforehand that these IDocs can actually be assigned to the current status of requests.
TIP: Also check transaction SM58 for problematic tRFC entries.
IMPORTANT: Notes 535172, 555229 and the above recommendations are relevant (unless otherwise specified) both for BW and for SAP source systems.

LSMW: Material Master Data migration

I will be migrating material master data using LSMW IDOC.
I also want to migrated associated material class data.
The question is:
How do I extract the material class data so that I can load them with LSMW IDOC CLFMAS after the materials are loaded?

Hi,
You have 2 possibilities.
1. If it is 1:1 transfer for source SAP system to target SAP sytem ( without data modification ) you to establish the ALE interface and distriute by using the prg: RBDSECLF
2. If it is a transfer of CLF data between 2 SAP systems where you need to modify the data based on some rules after you extract the data from the source system, you could extrace the data from Legacy by BAPI: BAPI_OBJCL_GETDETAIL. Once you extract the data, you could process as per the reqmt, & load the data by LSMW either by DI or by IDoc method.
Hope this helps.
Best Regards, Murugesh

Uploading picture to the material master data

Hi friends,
I searched the forum about this subject, however there are mostly answers related to retail sector.
I'd like to learn if ECC 6.0 could only itself is able to this. I mean is ECC 6.0 enough to add pictures to material master data or is there any configuration or customization requirement for that?
Thanks in advance.
Best regards,
Yusuf Gezer

yes, it is possible to store images to the materials. here you have at least 2 options, DMS and GOS.
DMS is document manament system, here it is even possible to classify the images for a better search. GOS is generic object services which is available in the maintenace transactions for material master and several other objects. Pretty easy to use, but....you cannot search for the images, you always have to go into the material and fom there you have to open the GOS to see whether an image exists or not.
further you should think about the place where you store these images and other attachments, I mean in SAP table system or in an optical disc system linked to SAP, which is much cheaper diskspace than the SAP tablespace.
A migration from DMS to DMS is relatively easy and can be accomplished with IDOCs via LSWM or ALE scenario.
Migration of GOS attachements is challenging. Nothing ready for use exists in SAP to do it.

Inital material master data load error

Hi experts,
We are on ecc 6.0 and gts 7.1.
While loading the initial material master data from R/3 to GTS,Transaction (/SAPSLL/MATMAS_DIRR3),I am getting the error ( for 1 material)-
Of 1 selected material(s), 0 were processed successfully
Message no. /SAPSLL/PLUGINR3112
When I try to load the required list of material, the error is same.
The RFC data distribution model is working for vendors and customers properly.
We want to use only compliance mngt and embargo functionality to block orders.
Can you give me some guidence?

Dear Milmuk,
it is hard to tell, why it is not working. There could be different reasons.
Please check if you have entered the correct data.
It could be that the relevant tables for transfer are not filled.
Please execute the following:
- BD53
- select message type (/SAPSLL/MATMAS_SLL)and edit it
- select a segment
- save
- deselect segment again
- activate
- set in trx BD60 the FM to the correct value
(/SAPSLL/MATMAS_DISTRIBUTE_R3)
You can than check with the programm: '/SAPSLL/PLUGIN_CHECK_R3' if
all 4 required tables (TBD24, TBD62, TBDA2, TBDME) are filled, or not.
If that's all fine I suggest you open a CSS ticket as then a more detailed analysis is necessary.
Christin

Material master data complete in bi - infoset or multiprovider

Hi all.
for one of the reporting requirement of my client i need to extract the complete material master data in BI - from MARA, MARC, MARD, MSTLB tabls.
which i have done and stored in the infoobjects - 0MATERIAL, 0MAT_ST_LOC, 0MAT_PLANT, 0MAT_SALES.
now user want to see all the information against each material in 1 single line the multiple lines will only come in when there is plant.
which approach i shoul go for this scenario.
infoset or multiprovider.
i created infoset by using inner join but then i see only common materials, left outer join is giving me problems.like -
Invalid or missing ON condition for left outer join (0MAT_PLANT)
Invalid or missing ON condition for left outer join (0MAT_ST_LOC)
Invalid ON condition for left outer join (0MATERIAL)
kindly give your suggesstions on this.
thanks
dipika

Hello,
There are restrictions regarding left outer join in infoset:
If a left outer join is used, the following restriction applies to the right table (right operand):
·        Only join conditions with exactly one other table can be defined and
·        This table in turn cannot be a right table (right operand) of a left outer join.
Tables connected with left outer joins always form the end of a chain of tables. In this way, as many tables as you want can be linked in an InfoSet with a left outer join to a core of tables that are connected using inner joins.
The restrictions on the definition of left outer joins are due to the technical limitations of databases. These restrictions do not apply to inner joins.
http://help.sap.com/saphelp_nw2004s/helpdata/EN/67/7e4b3eaf72561ee10000000a114084/content.htm
http://help.sap.com/saphelp_banking60/helpdata/ru/a3/96663bd194a978e10000000a11402f/content.htm
BR
Ondrej

How to maintain material master data in plant....

Hi all,
while creating BOM I am getting an error "no material master data in plant' can some one help me how to maintain the material master data in plant
Regards,
Balu

Hi,
Please check the below link for MMR creaion .
http://web.mit.edu/sapr3/windocs/bpmdb01m.htm
Regards,

How to maintain the material master data in plant

Hi all,
while creating BOM I am getting an error "no material master data in plant' can some one help me how to maintain the material master data in plant
Regards,
Balu

Check the material available in MARC table in SE11 transaction against your plant.If it is not available please maintain through MM01 transaction.

Runtime error while creating material master data

hello sir,
i am facing one prolem while creating MATERIAL MASTER DATA.
AFTER GIVING ALL REQUIRED INFORMATION WHEN I AM GOING TO SAVE THE DOCUMENT ITS SHOWING ABAP RUNTIME ERROR.
MESSAGE TYPE: - MDS_KEYMAP.
MESSAGE CLASS: 001.
PLEASE TELL ME WHAT TO DO?
REGARDS..

SIR THANK YOU FOR YOUR REPLY.
I ALREADY DONE THAT DUMP ANALYSIS.
SO PLEASE KINDLY GIVE ME IN DETAILS ABOUT THAT SOLUTION...

Can we recieve goods for purchase order with out material master data in PO

I have service PR for doing the services. I will give the material which is not accounted ( no material in the PO)and raise PO with reference to production order. but once the service is done,that product will become a material ( master data available) I have to receive the final product.Can we do the GR for this product. If so ,could you please explain the scenario

Hi Sankarkumar
When you are issuing the material for servicing your existing inventory for the material will be affected how you are plannignto handle that? You are receiving a different material once the serviceing is done then again yoour inventory will be affected for the new material. If you do not intend to issue material in SAP then why are you worried when you are bringing the new material into SAP after servicing is over? It is a subcontract scenario in a normal situation. But since you do not want then you can do a Service PO from the reqn and later use receipt without PO for bringing material in. Just speak to your finance guys how to set right the debit/credit amount resulted due to this transaction.
Regards
Sam

MM - Material master data - move standard field to another view

Hi everyone,
ÉCC 6.0 - release 7.0.
I've been adding many custom fields in Material master data MM01/02/03. Now I got a problem because we have to use a standard field in another view.
The field MARA-HERKL is set up to 'SV'(attribute V_130F-PSTAT):
Warehouse management = S
Sales = V
I want to add 'K - Basic data' in this field's attribute at OSMR Tcode , but this attribute is disactivated. I can not change this value.
I've check this note 306966 that mention: You cannot create new entries and delete entries in client 000. This client contains only the entries delivered by SAP which are used for distinguishing customer-specific fields and SAP standard during the maintenance of the other clients.
Is there any problem whether I delete this field and afterwards create it with the new values?
I'm not in client 000. So, I want to just make sure I will do a legal change.
thank you in advance,
Alexandre

None tips, Closed.

ALE:Material Master Data Distribution

Similar Messages

Maybe you are looking for