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

Similar Messages

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

How to get optional segments of Basic type ORDERS05

Hi All,
I am using ORDERS05 Basic type for one implementation where I need to use segment E1CUCFG of this basic type but it is not coming as this is optional segment. Please let me know how to get it.
Thanks !!

Hi,
In WE30, I can see the segment E1CUCFG for ORDERS05, If you want to use that, you will have to populate the same.
Regards,
Amitava

Tcode IDX2: Basic type 'MATMAS02' is unknown

Hi!
How to get the basis type such as MATMAS02, MATMAS05 as known basis type in tcode IDX2?
When I try to load metadata in tcode IDX2 I get the following error:
Basic type 'MATMAS02' is unknown
Message no. EA224
Thank you very much!
Holger

hi,
check the PORT is defined correctly in IDX1 in XI system.
Check SM58 in R/3 system..
check this blog as well page 9-10
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
Have you imported the IDOC into IR ?
Sachin

Idoc Reduction CREMAS

Hi,
Is there an alternative to this approach :
Problem: I create Vendor master idoc using basic type crema04 and message type cremas. Idoc reduction is present for this message type, so when the idoc is created only mandatory segment gets populated.
Solution I tried : Through BD53 , create a ZCREMAS reduction message type , select the segments to be populated , enable them and activate them . Use this message type for the generation of the idoc.
Question : Is there any alternative way to this method or this is the only way we can remove the idoc reduction for messag types?????
Thanks ,

Hi,
Perhaps you can use this custom exit '001' in include in include program LBD11F0Q to filter IDoc segment.
CALL CUSTOMER-FUNCTION '001'
 EXPORTING
 idoc_control_in = pxf_idoc_control
 target_idoc_type = target_idoctp
 target_cim_type = target_cimtyp
 IMPORTING
* idoc_control_out = pxf_idoc_control
 idoc_control_out = idoc_control_out
 TABLES
 idoc_data = pxt_idoc_data
 idoc_status = t_idoc_status.
This is being in FM MASTER_IDOC_DISTRIBUTE.
For SAP best practise, i would suggest to use reduce message type or segment filter.
Again, hope this will help.
Regards,
Ferry Lianto

Basic type 'MATMAS01' is unknown in SM58

I try to send IDOC to XI , i have done all settings when i send IDOC from BD10 i get error like that "Basic type 'MATMAS01' is unknown" by selecting message type AIDMATMAS.
but i have imported IDOC type "AIDMATMAS.MATMAS01" in integration repository already.
when i look at status of IDoc in sender system's WE05, last status is 03, not 12..Namely it doesnt reach XI.
what can it be the error ?
Thanks a lot

Hi,
Follow below configuration it will work i think it is due to customized idoc, once again check with segment, idoc and message type configuration and check whether all are released or not.
1. Check whether segment, idoc and message type are released or not.
2. Define Logical system and assign logical system to sender system (r3)
3. Define RFC destination in R3 system.
4. Define port and partner profile, in partner profile outbound window configure idoc parameters properly
According to ur requirement ur r triggering IDOC through abap program, check with control record parameters, some times due to control record parameters will throw error.
Once r3 configuration is over configure settings in XI
1. Import IDOC from r3 in IR window, if u getting any problem for import it will throw error. Check with basis team for authorization.
2. Configure RFC destination for R3
3. Configure IDX1 and IDX2 ports properly.
4. Configure scenario according to your requirement in IR & ID window
It will work without fail.

How to link a logical message to a basic type

hai gurus i am getting the warning that basic type is not linked with any logical message i tried with we82 but i am not able to fill the required fields can any one suggest the solution
thanx in advance
afzal

Hi,
First you have to follow the Steps to create customizes IDOC...
1. Define message types & Idoc Tpye using we30
2. Define Segments using we31
3 assign message type to Idoc type...we82..
In each and every step you have save and activate ..check whether it is active or not.....if it is not in active , you will not able to see your customized Idoc in you Idoc type list..
whenever u change an enry for extensiona and link to message type in we82 refresh in we20 by reselecting the message type.
Reward points
Regards

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

IDOC reduction for MSG type MATMAS

HI all,
i have a requirement where clients need only some standard segments and some particulars staructure.We are using MATMAS as a message type and MATMAS05 as a basic type.Basically it leads us for IDOC reduction. Can someone pls help me out for getting this requirement.
Rgds,
Raghav
Edited by: raghav on Jun 9, 2009 12:28 PM

Hi,
Launch the BD53 transaction (IDoc Reduction Maintenance: Initial Screen). In the Reduced message type field, type the value ZVISTAPM_REDUCED, then press the Create button. In the popup window which appears, type in the Message type reference field the value MATMAS.
Validate.
In the next popup window, type a short description for the new reduced message type.
Validate.
In the following window, select the segments and the fields needed for the new reduced message type.
Save.
KR Jaideep,

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

Article IDoc not getting processed in PI for particle article type

Hello All,
I have an strange behaviour in my system.
i.e 1, we are creating an article IDOC by using BD10 for particulat article type.
2, IDOC created succesfully , then
3, Process the IDOC in BD87 to push the IDOC to PI system .
4, But i could not see the message in PI that too only for one article type.
I'm wondering why this is not getting processed only for one article type and not for others.
we also checked the basic filter for the message type in dist model and even i could not see any condition in PI also,
Is there any thing else i should check? can you please help us on this.
Regards , Sethu.

Hi,
Try to reimport the metadata of IDOC into PI in idx2. Also check the port definition in ECC and whether the segment is released or not. Please go through the below discussions it may help you.
EDISDEF: Port XXX segment defn E2EDK35 in IDoc type ORDERS05 CIM type
IDoc 0000000000181226 was saved but cannot or should not be sent
Regards,
Priyanka

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

Basic type and idoc type

hi iam having z-basic type how to find what is the standard idoc type(for ex MATMAS,Creamas) for that

Step1. Go to WE30 and give the extended IDoc name
Step2. Check the extension button and click on display
Step3. Click on header button (Top 3rd left button)
Step4. In Technical Attributes, you will get the name under "Linked Basic Type"
Hope it solves your query...
Regards,
Prasoon Sahay
Edited by: Prasoon Sahay on Sep 2, 2009 2:18 PM

IDOC basic type

Hi guys,
Is there anyway to find out the right Basic type which suites our requirement?
Sahil

Hi Michal,
My requirement is whenever a material is created/changed an IDOC should be triggerd.
we are using change pointers concept here.
MASTERIDOC_CREATE_SMD_MATMAS is used to record the changes and its get triggerd when we create/change and then pass the idoc to PI for further processing.
I am also extending my IDOC by adding few fields.
My question is:
1.How do i know which basic type to use?
2.Do i need to populate the fields for an extended IDOC using some enhancements/EXITs or just pass the extended IDOC to PI?
please reply
Sahil

IDOC reduction gets always MATMAS05 as basic type

Similar Messages

Maybe you are looking for