Regarding MATMAS03 basic type

Hi,
I am using the segments E1MARAM, E1MARCM, E1MAKTM and E1MARMM
of MATMAS03 basic type for creating material.
The inbound FM used is IDOC_INPUT_MATMAS01.
But when I checked MM03 I can see only two views listed ( Basic data 1 and basic data 2)
What might be the problem. Waiting for your valuable inputs.
Regards
Vinitha

Hi Vinraj,
See the log, I think there would be some error messages also.
and aslo give E1MARA-VPSTA = KLVX in the idoc.
(Basic data - K, Storage - L, Sales - V, Plant stocks - X )
Please enter the relevant letter for a view which u want to create. If we dont provide data for the view, it will give error.
Reddy
Edited by: V.V.Reddy on Apr 30, 2010 8:41 AM

Similar Messages

IDOC reduction gets always MATMAS05 as basic type

Dear Gurus,
I am trying to create a reduced IDOC derived from MATMAS message. I get always an associated basic IDOC type MATMAS05 but I would like this concrete reduction to be derived from MATMAS03.
Can somebody tell me what can I do so the system will reduce from MATMAS03 instead of MATMAS05 ?
I am using release 470 for the application ERP and basis has release 620.
Thanks

Hi ,
When you are reducing the Idoc, system will consider latest version of the Basic type of mesage type MATMAS,
You can not reduce previous version, this is SAP standard,
You have to reduce MATMAS05 based on u r requirement and create new Message,
Revert back if u have any queries...
Regards
Suresh.,D

IDOC Segement Release vs IDOC Basic Type

Hi there,
we are in an upgrade project and are runing into a general question about idoc creation.
Here is our behavior:
1. We have an reduced IDOC Type in BD53 ZMATMAS based on Messagetype MATMASDI.
2. It has 2 Segements E1MARAM with fields MSGFN MATNR PSTAT and Subsegemnt E1MAKTM with fields MSGFN SPRAS MAKTX.
3. Done the things around (RFC, Partner Profile, distribution model, changepointer ..)
4. In Distribution Model in outbound parameters, added our ZMATMAS.
As parameters we have: Partner type: LS, Message Type: ZMATMAS, Basic Type MATMAS03! and Seg. release in IDOC Type 46B. The Partnersystem is an NoneSAP System.
We are using MATMAS03 because this interface exists since 46B.
Now we send an Material with BD10 and Message Type ZMATMAS.
The Master and Commuidoc are successfull created. In BD87 the commuidoc is an MATMAS03 and has the expected 2 segements E1MARAM and E1MAKTM.
But what we do not expect, if we look into the content of E1MARAM there are ALL Fields which exist for the E1MARAM in release 7.00. Not only our 3 fields MSGFN MATNR PSTAT, or as we second expect only the segemnts that had existed in the segemnt E1MARAM in release 46B of MATMAS03.
The additional fields were filled with the NODATA sign.
My question is: Is it correct that an IDOC with basic type MATMAS03 can have an segement E1MARAM which is formated like the segemntdefinition E2MARAM007 (Release 7.00 / 6.03)?
The difference is definatly the length of the field! 876 in 7.0 vs 757 in 4.6A.
Why is SAP using the highest available segemnt release regardles which basic type we choose?
Isnt this wrong?
Additional infos:
We know that it is not possible to have an IDOC with basic type MATMAS03 with an segement e.g. E1MARA1 which only exists in newer basic type MATMADI if segemnt release is set to 46B in our distribution model.
Failure is: Segment E1MARA1 is unknown in Release 46B/ (correct and expected behavior)
If we are using this scenario with not an reduced message type, we will only find the fields in E1MARAM which are filled with data. (Not all fields of the latest release with nodata)
I traced the MASTER_IDOC_CREATE_MATMAS and hit the function IDOC_REDUCTION_FIELD_REDUCE. As you can see in it, it first checks if the idoc is an reduced message type, and at the end, fills up all fields with the "empty_symbol" which have no data in it. Why is this only happening if it is an reduced message type?
Kind regards
Manuel

Additional Info:
In WE21 at the TRFC Port, it is possible to set this Option:
Send Only Fields of Selected Segment Version
The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
But if we are using an reduced message type, all fields of the newest release are in the segement.
The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
But it is never called when createing an material IDOC with BD10.
Bug or feature?
Kind regards
Manuel

BASIC TYPE VS MESSAGE TYPE

Hi all,
Can i know wats the difference between Basic type and Message type??
wat s the use of having both this types????

hi
Message Type:
A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterises the data sent across systems and relates to the structure of the data called an IDOC type.
Diff. with IDOC type
An IDoc type specifies the structure of the data.
A message type specifies the meaning of the data
Diff. b/w IDOC type and IDOC
An IDoc type is the definition of a specific data structure.
An IDoc is an actual instance of data based on an IDoc type. Therefore, there can be many IDocs created from a single IDoc type.
Every idoc type will have Message Type.
It mean Idoc will be recognised By message type.
For ex : MATMAS03 is idoc type, and its message type MATAMS.
There are different message type for every master data. suppose for vendor master CREMAS is the message type, for customer mast DEBMAS like these there many message type for other type of master data.
To recognise the particular idoc, we use message types.
We82 is the TCode where IDoC type is attached to Mesage tYpe.
Refer to this related thread
difference between message type and idoc type
Check 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://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
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
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Regards
Anji

Error in idoc of basic type artmas05 - status 51 with Message no. MG537

Hi all,
I tried to upload the material master table through idoc creation of basic type artmas05. But when i'm trying to do that i'm getting status 51 with Message no. MG537. then I analysed the application log which displays the following
*The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required
field; it does not contain an entry
*The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
*The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
*You have not fully maintained the tax classifications
*The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
But i hv given values for all the above fields in their respective segments.So can any1 suggest me how to proceed further.
It would be helpful if someone could tel me the required fields in idoc to upload material master table through idoc.
Thanks in advance,
Revathi.

Hi,
Anybody please tell me the reason for the following error, despite giving all the field values mentioned there. The same error occurs even if I run the BAPI (which the ARTMAS iDoc uses) directly by passing values.
The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required field; it does not contain an entry
The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
Regards,
Gowri.S

Msg basic type idoc_type unknown ?

Hi,
i am workin on file 2 idoc scenario.
on XI created rfc destination using sm59
         went to idx1 created port and assigned the rfc destin
    In idx2 i was able to load one idoc but remaining
     shows the message basic type <idoc_type> unknown.
Can any one help??
regards
fariha

Hi Kazi,
for File to IDOC no need for IDX2
Check my link at wiki for File to IDOC
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC&
Sachin

Inbound IDOC basic type HRMD_A07: Why no validation available?

I am using a standard inbound IDOC basic type HRMD_A07 to update employee master data (IT0000 & IT0001). However, i found out that this IDOC just directly updates to the infotypes without any validation. For example, i provide an invalid company code (BUKRS) and personnel area (WERKS), the IDOC still updates into database without any proper validation.
Filled the following fields in the IDOC segments:
E1PLOGI
plvar=01, otype=P, objid=00000001, opera=I
E1PITYP
plvar=01, otype=P, objid=00000001, infty=0000, begda=20120101, endda=99991231
E1P0000
pernr=00000001, infty=0000, endda=99991231, begda=20120101, massn=01, massg=01, stat1=3, stat2=3
E1PITYP
plvar=01, otype=P, objid=00000001, infty=0001, begda=20120101, endda=99991231
E1P0001
pernr=00000001, infty=0001, endda=99991231, begda=20120101, bukrs=XXXX, werks=XXXX, persg=1, persk=EC, abkrs=99, plans=00000111, otype=S
Please help me out in case I am missing something. Thanks.

Additional Info:
In WE21 at the TRFC Port, it is possible to set this Option:
Send Only Fields of Selected Segment Version
The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
But if we are using an reduced message type, all fields of the newest release are in the segement.
The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
But it is never called when createing an material IDOC with BD10.
Bug or feature?
Kind regards
Manuel

Fill IDOC segment, E1IDBW1. For PEXR2002 Basic Type

Hello Team.
We send the IDOC for the Basic Type PEXR2002, Message Type PAYEXT.
This IDOC doesn't fill the Segment E1IDBW1 (IDoc header - special instructions (INP) )
I'm review some notes(1164524) and said to fill this segment it's neccesarie config the IHC.
But doesn't have this functionality.
It's possible fill the segment E1IDBW1 in a user exit or any other enhacement at creation idoc moment?
My idea is used the FM
CALL FUNCTION 'GET_SEGMENT_POS_FOR_INSERT'
    EXPORTING
      I_BASIS_TYPE            = ch_edidc-idoctp
      I_EXT_TYPE              = ch_edidc-cimtyp
      I_SEGMENT_TYPE          = 'E1IDBW1'
    IMPORTING
      E_INDEX                 = li_tabix
    TABLES
      IT_EDIDD                = t_edidd
    EXCEPTIONS
      BASIS_TYPE_NOT_FOUND    = 1
      EXTENSION_NOT_FOUND     = 2
      EXTENSION_ERROR         = 3
      INVALID_IDOC_DEFINITION = 4
      IDOC_ERROR              = 5
      INVALID_SEGMENT_TYPE    = 6
      INVALID_START_INDEX     = 7
      NO_MORE_POSITION        = 8
      TOO_MANY_SEGMENTS       = 9
      OTHERS                  = 10.
To Fill 2 constants in this segment.
Do you have any other idea?
Thanks
Edited by: David Lezama Gonzalez on Sep 1, 2011 2:51 PM

Hi,
Basically the segment E1IDBW1 will always be filled via user exit.
If you work with the IHC (In-House-Cash) application you have to fill
the E1IDBW1 segment as described in note 626577.
If you don't work in an IHC environment the following conditions must
be fulfilled:
1. The payment program has to fill certain fields (e. g. REGUH-DTAWS,
REGUH-DTWS1 - REGUH-DTWS4).
2. If this is fulfilled the payment data (REGUH, REGUP tables) will
be filled. The instruction keys will be moved to IDOC segment
E1IDKU3.
3. In user exit EXIT_SAPLIEDP_002 you can take over the instruction
keys from segment E1IDKU3 into E1IDBW1.
You may also read note 496663, this note explains about user exit
EXIT_SAPLIEDP_002 to populate this field in the idoc.
Also, you can check the note:
580321 - RFFOEDI1: BTE process 00002441 (Change IDoc)
REgards,
Cristiano

Trigger workflow when IDOC Status 51 & with Basic Type "ORDERS003"

Hi Experts,
Can any one explaine how to create worlflow for "When Idoc status is 51 with the combination of Basic Type "ORDERS003" . If this condition will satisfy i need to send a mail using worklflow. For this one Bussiness type is BUS2102".
Can you explaine any one please i am new to Workflow.
Regards,
Sri

Hi,
Please refer to the below thread. Hope it helps.
Triggering workflow upon idoc fail
Regards,
Sridhar

Required Outbound Process Code for MessageType LOIPRO (Basic type-LOIPRO01)

Hi EDI Gurus,
I need to know the outbound Process Code for MessageType LOIPRO (Basic type-LOIPRO01).

Hi,
there is no process code for MessageType LOIPRO .
check the below link u will get the clear idea.
Re: Process Code for Outbound Production Order??
Reward if helpful.
Regards,
Nagaraj

IDOC question on Message type and Basic Type - Partner Profile

Hi all,
I am wonder if I can post any IDoc question in this right forum/module. If not please direct me to the right forum/module. I am a newbie in IDOC setup.
My question is about the setup of Partner Profile creation (WE20).
When creating a new partner, for example with partner type LI, I notice there is outbound parameter and inbound parameter.
Questions:
1 u2013 It makes sense to have only one message type record appear in EITHER one of these two tables. I notice that some partner in my system has message type record exist on both the inbound and outbound parameters table, why system allows? What is the business rational?
2 u2013 May I have a list of standard SAPu2019s Message Type object of its usage description, and its allowable Basic Type (ie. IDOC TYPE). Basically a website to describe their (i.e. Message type and its Basic Type) business usage.
Thanks.
tuff

Tuff,
Below are my thoughts,
There is a partner sing partner type LI. This partner in the WE20, has one record (i.e. with Message Type ORDERS) exist in the Outbound Parameter table. This partner also has 4 records (i.w. with Message Type DESADV, INVOIC, MBGMCR, and ORDRSP) exist in the Inbound Parameter table. So my question is what is the business rational behind this kind of setup. Because I am confuse when come to create a partner profile, whether I need to create a message type in Inbound Parameter table or Outbound Parameter table, or I need both.
OK, so looking at the above example, you have an orders message type(This is for creating an order) in the outbound, this means that you are sending out an IDOC(purchase order for ex) to this partner, so that this partner can create an SO in his system and fulfill your order.
Now you also, mention that you have other four Message types for the same partner on the inbound, now let us look at the above scenario, you have asked your partner to fulfill the order, i guess you would like to get a confirmation from him/her if the order was created or not in his/her system and how and when is he/she going to fulfill your order requirement. This he/she does by sending an response to your order - ORDRSP.
And when the partner is ready to ship your order to you, he/she sends out a Advance Shipping Notice - ASN via the IDOC of message type DESADV.
Finally and most importantly , he/she will send you the invoice - INVOIC for the order.
In general, you interact with your partner via Business Docs - Order, Delivery, ASN, Invoice etc, so whatever document come from your partner - ORDRSP, INVOIC etc will be on the inbound profile of the partner. Whatever docs that you send ORDERS, ORDCHG etc etc will be on the outbound profile of the partner.
2 - Bascially I would like a reference in any website that allow me to choose which message type is best use for my partner profile, so that I don't have to reinvent.
Well, there is no choice of choosing/best message type for a given requirement - So for sending an Invoice the message type is INVOIC, ORDERS - For order creation, ORDCHG for order change etc. However the IDOC type, is some thing that you can choose, for Ex: ORDERS01 - ORDERS05, these are the IDOC types that are available, so if you are interacting with a partner who are running an old version of SAP and their system has only upto ORDERS02 in their version of SAP then you would use ORDERS02.
Regards,
Chen

Processing IDOC Basic type ORDERS05 in CRM...

I'm processing (via WE19) an IDOC (Basic type ORDERS05) to create a Sales order withing CRM. I'm getting there in that a sales order is being raised, although there is no item level details so far. I know that config of the system plays a big hand in what fields within the IDOC need to be populated but has anyone actually posted/raised a Sales order in this way and can you tell me what fields within the IDOC are mandatory. Or perhaps suggest how I might derive this.
Ideally I wanted to extract a sales order and produce an outbound IDOC and then compare the contents, but I can't (don't know how) do this.
Any help would be greatly appreciated.

Hi Garry,
Here is an order from WE19, which works
        E1EDK01
     ACTION: [QUAL] - suggesting 000 - no changes
        E1EDK14
     QUALF: [QUAL] - suggesting 008 - sales org
     ORGID: [ORGANIZATION] - anything you have defined /your side/
        E1EDK03
     IDDAT: [QUAL] - suggesting 002 - delivery date
     DATUM: [DATE] - any date
        E1EDKA1
     PARVW: [QUAL] - may use AG as 'sold to' here
     PARTN: [PARTNER#] - any partner defined
        E1EDKA1      - not necessary
     PARVW: [QUAL] - may have different 'sold to' and 'ship to' or 'bill to'
     PARTN: [PARTNER#]
        E1EDP01
     POSEX [ITEM#] - for example '1'
            MENEE [Unit of measure] - PCE for peaces
                 E1EDP02
               QUALF: [QUAL] - suggesting 001 - customer order
               BELNR: [document number] - document #. any
                 E1EDP20
                WMENG: [Scheduled quantity] - any - quantity
               EDATU: [Date] - any - when to deliver
                 E1EDP19
               QUALF: [QUAL] - for example 001 - used by customer, 004 - used by manufactured
               IDTNR: [material ID] - material ID
        E1EDS01
     SUMME: [Total value of sum segment] - check for the number of lines in PO1.
Hope this helps and do not forget to allot points.
Regards,
Martin

IDOC communication between different basic type releases.

Has anyone run into a scenario where a newer SAP release would like to send a message to a partner with an older SAP release, using a basic type that does not exist in the older system? (eg. DELVRY05 which only exists in release 700)
In this scenario, what is the best practice, other than to have the newer SAP system send an older basic type that does exist in the receiving partner?
Thanks.

Hi,
You can do this by specifying the older release in the partner profile outbound settings (for message type).
Under the "Outbound options" tab there is a field "Seg. release in IDoc type". There you can specify the older release and the IDoc will automatically be depricated when it is received in the receiving system.
Regards,
Gajendra.

Basic type CREMAS03 does not exist

Hi all.
We have SRM 7 Classic Scenario with ECC 6.4
My problem is in scenario MM-SUS. When we try to replicate a vendor data from MM to SUS the idoc MM is processed correctly, but in (SUS) has an error in trx WE05: Basic type CREMAS03 does not exist.
I review the settings and I can not find the cause.
any idea about that?
Regards

Hi,
I am not clear with your issue. Why are you checking for idoc status in SUS system?
IDOC is sent from the ERP system and check what the status of IDOC is in ERP. Next check whats the xml status in PI system and if its successful in PI then check xml in SUS system/. You can check xml status using tcode: sxi_monitor.
Regards
Sam

Basic type for product hierarchy v/76

Hi all,
I have another task that need to configure once a product hierarchy is created in Tcode v/76, it will trigger an outbound IDOC and send out.
Can anyone explain to me what basic type or message type should be used in this case?
Thanks for help.
Best Regards,
JL

Hi,
I am having the same issue, to send prod-Hier via Idoc.
Please let me know if you get the solution for the same,
BR,
Udit

Regarding MATMAS03 basic type

Similar Messages

Maybe you are looking for