MATMAS idoc with classification details - reg

Hi,
I am working in a project related to the transfer of Material Master from one system to another ( Both are R/3 systems).
I am currently using the message type MATMAS with basic type MATMAS05. With the above message type i am able to generate an idoc from source system with all of the details except for the classification details.
For classification i have configured the message type CLFMAS and CHRMAS, in the CLFMAS i am able to successfully generate an idoc with BD91/BD92 tcodes. But when the idoc is generated, the idoc gives the list of charactersistics managed in the class at each segment level but not able to retrieve the values maintained by me during the material master creation. In order the target values for each of the characteristics in the class is empty.
Please clarify me with the following queries:-
a) Is that really required to push both CLFMAS and CHRMAS for a material master classification related field values ?
b) How to get the characteristics values maintained in the material master at the idoc level ?
c) How to link the CLFMAS generated idoc and the MATMAS idoc to link the relationship?
Thanks for the understanding.
Thanks and Regards,

Classification of a material has to be send with CLFMAS IDOC separate from the material.
Usually you first distribute all characteristics and classes, then the materials, finally the classification.
You have to enter the new material number in segment E1OCLFM field OBJEK of your classification Idoc.

Similar Messages

MES Interface Development (Standard IDOC-MATMAS enriched with Z-Fields)

Hello Everyone,
We have an issue that we want to sent IDOC data to our local MES System. The XML Target Structure of the MES System is given and cannot be changed.
Most of the fields to be sent are in the MATMAS IDOC but some fields need to be enriched with material classification data which are maintained for each material individually in the ERP. To retrieve the data out of ERP we using the u201CBAPI_OBJCL_GETDETAILu201D. Here we perform an iteration about all these fields to read the classification description and the associated characteristic value. Sometimes it can happen that not for each material the value are maintained and then we are getting blank values
Now I coming back to my main questions.
The target structure of the MES XML File is given and need basically just two core segments from MATMAS IDOC.
E1MARAM SEGMENT="1" -> Key fields needed: Material Number, MEINH, EAN Number etc.
E1MAKTM SEGMENT="1" -> Key fields needed:: Material Description
The n- Classifcation field need to be listed directly under the segment E1MARM Segment. So the target structure need to be dynamically built with these n Z Field under den Segment with the following structure.
E1MARAM SEGMENT="1" Material Number, MEINH, EAN Number etc.
1
u2026<ZL161AUSPM SEGMENT="1">
 <ATNAM>MGBEZ_</ATNAM>
 <ATWRT>Galenical Bulk Prod.</ATWRT>
..</ZL161AUSPM>
n
E1MAKTM SEGMENT="1"  Material Description
As stated out above the information from the classification data are filled in an internal table (XML document with several Row)
Questions:
How do I get the information from the internal XML Document into such ZL161AUSPM structure. Shall I rename the rows in the XML Document from Row to <ATMAN>? And how is this possible? I assume that I cannot change the row name in an "MII XML Document"
<?xml version="1.0" encoding="UTF-8"?>
<Rowsets DateCreated="2009-09-04T14:24:58" EndDate="2009-08-31T14:43:13" StartDate="2009-08-31T14:43:13" Version="12.0.6 Build(12)"><Rowset><Columns><Column Description="CHARACT" MaxRange="1" MinRange="0" Name="CHARACT" SQLDataType="1" SourceColumn="CHARACT"/><Column Description="CHARACT_DESCR" MaxRange="1" MinRange="0" Name="CHARACT_DESCR" SQLDataType="1" SourceColumn="CHARACT_DESCR"/><Column Description="VALUE_NEUTRAL" MaxRange="1" MinRange="0" Name="VALUE_NEUTRAL" SQLDataType="1" SourceColumn="VALUE_NEUTRAL"/></Columns><Row><CHARACT>CH0_MES_01</CHARACT><CHARACT_DESCR>CH0_MES_01</CHARACT_DESCR><VALUE_NEUTRAL>AT</VALUE_NEUTRAL></Row><Row><CHARACT>CH0_MES_16</CHARACT><CHARACT_DESCR>CH0_MES_16</CHARACT_DESCR><VALUE_NEUTRAL>AAI-WC</VALUE_NEUTRAL></Row><Row><CHARACT>CH0_MES_01</CHARACT><CHARACT_DESCR>CH0_MES_01</CHARACT_DESCR><VALUE_NEUTRAL>AT</VALUE_NEUTRAL></Row><Row><CHARACT>CH0_MES_05</CHARACT><CHARACT_DESCR>CH0_MES_05</CHARACT_DESCR><VALUE_NEUTRAL>10000.0</VALUE_NEUTRAL></Row></Rowset></Rowsets
How do I get the dynamically the structure under the E1MARAM SEGMENT="1"? with n u2013 integration? This mean if the material has been assigned three characteristic then I need three time the structure under the segment u201CE1MARAMu201D
Is someone experienced with interface development of such Z-Message respectively has someone an idea or guideline to dealt with such issues?
Thanks in advance,
Markus
PGST
PT Business Solution Management- Manufacturing
F. Hoffmann-La Roche Ltd. Switzerland, Basel
Edited by: Markus Schmeckenbecher on Sep 4, 2009 2:33 PM

Markus,
it is a bit difficult to get the structure from your post, but when I get it right you need to add new nodes in a predefined xml structure.
Did you have a look at the Link editor action "Data Item" from the SAP xMII XML Output? You can define a name and value and add it to a given xml structure. A problem might be the target xml if it is not an IlluminatorDocument (which is of kind /Rowsets / Rowset / Row).
If this does not work, you may try to build Local xml structures for all your Z fields, and append those xmls to your target, using the Link Editor Append XML function.
Michael

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

Error : No authorization to send IDocs with message type MATMAS

Hi All,
My scenario is FILE-XI-IDOC.
I am getting chequered flag in SXMB_MONI,but in that under outbound status I am getting red flag.
When I check in SM58 I am getting message as "No authorization to send IDocs with message type MATMAS".
Do I need to give any authorizations on XI side or on R/3 side?
If so, what is the authorization required?
I could not find the note :837595.

You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.
This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
Solution
In transaction PFCG, extend the role of the logon user by adding the following authorizations:
Authorization object S_RFC
 Field name RFC_TYPE value FUGR
 Field name RFC_NAME value EDIMEXT, SDTX
 Field name ACTVT value 16
Authorization object S_IDOCDEFT
 Field name ACTVT value 03
 Field name EDI_CIM value ' '
 Field name EDI_DOC value TXTRAW01
 Field name EDI_TCD value WE30
Authorization object S_CTS_ADMI
 Field name CTS_ADMFCT value TABL
Authorization object S_TABU_DIS
 Field name ACTVT value 03
 Field name DICBERCLS value
from the note mentioned above.
Regards
Bhavesh

Batch classification details -mass check -reg

Hi ,
Requirement is as of now batch classification details of a material are checked through MSC3N , where material , plant etc.. are entered and executed .
here we can see for the list of materials one by one only .
is there any t code through which the details can be checked entering materials in multiple / entering material type
if not available in standard SAP , if an ABAP report to be made , please suggest the flow with tables and fields
inputs
material type
material
plant
batch
storage location
out put should be teh batch classification details
Is there any Tcode similar to MSC3N where multiple inputs can be given / details can be taken in mass not entering one by one
pl

Dear,
Please check to table MCH1, AUSP, KSSK, KSML, KLAH
Use these FM.
CLAF_CLASSIFICATION_OF_OBJECTS
[Thread|Re: Get batch characteristic value]
Regards,
R.Brahmankar

Multiple MATMAS IDoc getting created through RBDMIDOC program

Hello All,
I am creating MATMAS Idocs by RBDMIDOC proram, but as MATMAS message type is used in multiple distribution models ( i.e. MATAMAS is being sent to multiple partners), its creating multiple IDocs.
I want my IDoc to get triggered only for a particular partner. How can i acheive this ?
Searched on SDN but did not found solution.

As the standard settings, IDOCs will be transmitted to all the Partners which are maintained in WE20 (Partner Configuration). You can restrict the triggering of IDOC based on some condition using the Business transaction event MGV00100 (Publish & Subscribe). This event is called from Function module MASTERIDOC_CREATE_MATMAS (Line number 2074). Documentation of Standard FM SAMPLE_INTERFACE_MGV00100 reads
* Event rissen by the ALE outbound process for MATMAS.
* It allows to modify the idoc's control header the idoc data aswell
* as serialization information created by the standard SAP outbound
* process.
* Raising the EXCEPTION ERROR will prevent the IDOC from being
* submitted to the ALE layer.
* BE CAREFUL WITH ANY CHANGES TO IDOC_CONTROL. IT MAY EFFECT YOUR WHOLE
* ALE-SCENARIO
You have to copy the Standard FM SAMPLE_INTERFACE_MGV00100 to a Z function module and assign it using transaction code FIBF. Search SCN to get more details about configuring Business transaction events using FIBF.

ALE , EDI and IDOC with MM??

hii
What is ALE, EDI and IDOC in SAP??
How its linked with MM??
Explain the above things with example
Thanks

Hi!
IDOC = Intermediate Document
IDoc or Intermediate Document is a standard SAP document format. IDoc's allow different application systems to be linked via a message-based interface.
For more detailled information look in SAPNET under
http://service.sap.com/EDI
For exapmle in purchasing:
The IDoc message type ORDERS is used to send a purchase order to a vendor.
EDI = Electronic Data Interchange
EDI stands for Electronic Data Interchange, which means that data is electronically transmitted from one system to another. The main requirement of EDI is that the systems of the communicating partners understand each other. Usually, the data from one partner gets mapped into the format of the other partner and vice versa.
Supporting this there exist EDI standards (named EDIFACT, ANSIX12, ODETTE, VDA, TRADACOMS, SPEC2000, ...), where the data formatting for exchanging documents are specified. Normally the partners agree using a special standard message (for example EDIFACT message ORDERS for a purchase order).
In the SAP system the outgoing data are stored in IDoc format. When processing a receiving document, the Inbound SAP system receives the data in IDoc format too.
Further processing (converting/mapping from IDoc in another format and vice versa) depends on the partner agreement:
If the partners have agreed using a special EDI standard, mapping between IDoc and the EDI standard is necessary. This mapping is not supported by SAP, external converters or EDI subsystems must be installed by the customers for this purpose.
If both systems use SAP software, there is usually no need for mapping (which can save users a lot of money). The two systems are often connected via ALE (Application Link Enabling).
If partners are using XML, the SAP Business Connector can be used. The business connector is a tool used to help customers connect via EDI. It includes routing and mapping and is XML compatible. To read more about XML at SAP go to SAPNet Alias 'XML' (http://intranet.sap.com/XML).
For example:
Vendor can send the invoice by EDI creating an IDoc with message type INVOIC using IDoc Type INVOICxx. He can determine (depending on the partner agreement) how to create an IDoc for Inbound processing with FI or MM-IV.
ALE = Application Link Enabling
ALE is short for Application Link Enabling. Special Basic programs support this functionaliity (see documentation of BC_MID_ALE).
To link applications you have to configure an ALE model. It contains all relevant data about how a system's configuration (normally a central system and assigned local systems) exchange data.
With help of the ALE technology, the distribution of contracts is possible in MM via the following business process:
Contracts that a central purchasing organization distributes to local purchasing organizations to allow the latter to utilize the more favorable conditions they contain for the procurement of materials or external services.Each local purchasing organization sends information on its own release orders back to the central purchasing organization.
For this purpose the contract in the central system can be copied to the local systems (with message BLAORD and COND_A). When a release order to a distributed contract is created in a local system, the release docu is automatically sent to the central system (with message BLAREL) updating the release docu of the contract in the central system.
Precondition for this scenario is, that in all systems the used master data (material, vendor, sources of supply, ...) are the same. This master data can be distributed by ALE, which should be done before sending the contract from the central system. Available message types for distribution of master data are:
MATMAS (ARTMAS in retail system) for material master
CREMAS for Vendor master
INFREC for info record
SRCLST for source list
COND_A for conditions of info record
SRVMAS for service master data
Technical documentation to ALE can be found by path:
Basis Components / Middleware (BC-MID) / Application Link Enabling (BC-MID-ALE)
The most important Transactions for testing Idoc:
WE02 Display IDOC
WE05 IDOC list
WE19 Testing IDOCs
BD87 Status Monitor for ALE Messages (reprocess)
Notes:
456127 FAQ: Electronic Data Interchange (EDI) in Purchasing
536411 Sample scenario for ALE contract distribution (only internally released)
I hope I could help you fruther
Best regards
Erika

Error in Receiver - IDoc with errors added

Hi All,
I am getting error in 56 - IDoc with errors added in receiver System.
I am new in Idoc - please tell me How to resolve this issue..
Thanks in advance..

Hi all thanks for reply .
All are the help full answer ,
I use T-code WE19 and change partner profile and execute now it is fine.
But i have checked all configuration regard partner profile from T-code WE20 it looking everything is fine but in Test tool for Idoc Processing by t-code WE19 i have checked it will taken wrong partner profile detail after giving correct manually now it is working fine.

How to Test, Inbound idoc ,with out the Sender System, using a Text File

Hi Guru's .
we wanted to test BLAORD03 inbound idoc (Message Type BLAORD).with out the SENDER SYSTEM.
on the same client.
we wanted to test this idoc with text file from our local machine.
Can anyone give us detail steps.like how to create File layout
with Segment name,and values for the fields.how to pass this file to the system.
Thanks in advance.

Hi Aparna.
My requirement is to test the idoc with Inbound File.
Generate a file with the data entered through segments through we19 ,and use the same file for processing through we16.
when i am trying to do this syst complaing about
Partner Profile not available, and some times
port not available. and some times with
'No further processing defined'.
but i maintained part profiles and port perfectly.
Can you help me in testing with test 'File' port.

Bdc for MM01 with classification view

Hi all,
I need to create materials using mm01 with classification view. since there is no bapi supporting this view, i am ding by bdc.
The problem is in classification view once i give the class type and name a screen pops with caption
characteristic value assignment, but theere are no charateristics displayed - wat values do i have to enter here >
once i leave this screen the characteristics show up one after the other and i can load the details. but then while tryin to save error comes staing incnsisitent value assigned. wat do i ener in the intermediate screen t avoid this error.
thanks

hi when you are creating a classification view with characteristics.. you need to do all at once... you cannot modify..
all you can do is delete the whole view and create with all the changed again.. I dont memorize the BAPI .. but you have BAPIdelete.. BAPIadd..

How to isolate error with a record/segment in IDOC with multiple records

I have an IDOC with multiple records/segments (typically 1000 records/segments). Sometime XI can not process the IDOC because of some control characters in data.
1. How can I pre-processed the IDOC to remove those control characters?
Can I use XPATH expression/Java class to do it? How can I configure the XPATH expression/Java class in XI to pre-process the file?
2. Until I have answer to 1st question. I would like to find out the error is exactly for which record? What configuration can I do in XI to isolate the error is with which record/segment in IDOC?
Thanks in advance.

Split the IDoc.
with in the UDF, after the validations if every thing fine, pass as successful records to success_MT and pass it to target system using Branching in BPM.
if errors found in the record, then store the error records in Hash table with in UDF, get the IDoc number, frame as a string and raise alert.
U have to do this in the context of IDoc.
If U wanna get the IDoc Number, Segment Name and field name for every failure, U can pass the expected error field name as constant to UDF, frame the sentence in the UDF like -> IDoc 1234321 segment SEG001 field FLD03 has a special character *.
If U wanna pass this string to source/target, U can do in error messages branch in BPM.
U must use BPM for splitting the IDoc, since it is multi-mapping.
reg.,
Yallabandi.

Filtering out MATMAS IDoc based on a condition

Hi All,
 We are distributing a Material Master IDoc (Message Type MATMAS / IDoc Type MATMAS05) from an ECC 6.0 (WebAS 700) system to an external Non-SAP system via SAP XI.
 Now our requirement is that the users will maintain a Z-table with all the SAP plants that are relevant for the external system. They can add or delete plants from this table in the future
 If the MATMAS Idoc is created/extended for a plant which is not in the Z-Table then it should not get distributed.
E.g. If MATMAS IDoc contains plant 5000 and 5000 is not in the Z-Table then the Idoc should not even be created
We Tried a lot of enhancements: -
SMOD Enhancement - MGV00001
Enhancement Spot - ES_SAPLMV01 at different call up points
But none of them give the required exact result.
If we implement the enhancement spot inside the function module MASTERIDOC_CREATE_MATMAS, we get a message "1 Master IDoc created, 0 Communication IDocs created". So something is getting created and that's incomplete anyway.
So I am not sure how reliable this is
One last approach I have is: -
1) Send the IDoc to XI (without filtering)
2) Let XI look at the Plant code and compare with the Z-Table in ECC (via a Z-RFC function module) and then decide whether to send the IDoc or not send it to external system
Please let me know if my approch is correct or I am missing something here
Thanks and Regards,
Aditya

Hi Aditya,
If the Communication Idoc is not created it means that the IDOC is not sent out of the system. The Master Idoc creation does not mean the Idoc is sent to the XI adapter.
The purpose of Restricting at the Plant level will be satisfied if you delete the Idoc data with in the function module MASTERIDOC_CREATE_MATMAS.
It will work. Consequently you can add an additional check in XI to do this check, but this will increase the number of connections made to R3.
Hope it helps.
Thanks,

IDocs with incorrect status

Hi !
When i tried to upload data from R3 to BW based on generic DataSource
( function module ) , in the monitor i get the following error :
Status code : 56. Description: "Idoc with error added" .
How can i get more details about the error? How To correct the Error ?
Thanks
Moshe

Hi,
it's IDoc with errors added
check if you have any errors in other stauses
and display 56 (double click) in WE02
you should see some more descriptions .
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
Refer
https://forums.sdn.sap.com/click.jspa?searchID=4344391&messageID=3662902
Foe more information, please check this links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
rEGARDS

Material master - classification details

Hello,
we have material master with classification view- active
now i wanted to down load all the materials - classification details (value maintained for the characteristics in classification view)..
is there any table from which i can down load the same>?

CABN                           Characteristic
CABN_EXCL                      Characteristics That Are Excluded for Type Matching
CABNNEW                        Characteristic
CABNT                          Characteristic Descriptions
CAWN                           Characteristic values
KSML                           Characteristics of a Class
LCABN                          Characteristic
LCABNT                         Characteristic descriptions
LKSML                          Characteristics of a Class
AUSP - Char Values
Regards,
Ashok

Idocs with error status

Hi Everyone,
How to find all idocs with error status for a given date range?

Hi,
Please refer EDIDS for Status and EDIDC for control records.
Also refer the below wiki page for details.
http://wiki.scn.sap.com/wiki/display/ABAPConn/IDoc+Overview
Thanks,
Karthik

MATMAS idoc with classification details - reg

Similar Messages

Maybe you are looking for