Idoc Message type & Basic type

Hi All,
Can any one tell me what is the <b>Message type & Basic type(idoc type)</b>
of <b>Goods received</b> for inbound & outbound
Thanks
Sunil

refer view V_TBDMS in Sm30 transaction
check message types -
ACC_GOODS_MOV_REVERSE
ACC_GOODS_MOVEMENT
DANGEROUSGOOD
GOODSMVT_SAPCREATE
MBGMCA
MBGMCR
WGSREQ
WMMBXY
WPUWBW

Similar Messages

Idoc processing - determine Basic Type in Program

Hi Forums,
I would like to determine the Basic type that is being processed by at the time of my Idoc creation.
the function module I am using is being called by shipping document as well as delivery documents.
I would like my code only to be executed when it is a basic type of DELVRY05

Hi,
1) Goto Tcode - we57:
Assign function module to IDoc type
Module: Function module
Basic type:
Message type:
Direction: 2 (inbound)
This will differentiate between Shipping and Delivery.
2) Creating Inbound process code - we42
For Outbound Process Code -- WE41.
For further plz refer following link.
https://wiki.sdn.sap.com/wiki/display/ABAP/ALE%2CIDOC
Thanks and Regards,
ShreeMohan

What is message type, basic type and logical message?

I have a question with EDI.
What is message type? what is basic type? what is logical message?
I am a bit confused. I appreciate your links that you may provide, but even if you can brief me in a few sentences, that will be great.
Thank you,
Krishen

A Message type indicates the type of business document that you are trying to transmit or receive.
A BASIC type is the IDOC type, which is the actual document that is being exchanged. A message type can be associated with different IDOC types and depending on the requirement you can choose the appropriate one.
A logical message is nothing but the message type.
Regards,
Ravi
Note : Please mark all the helpful answers

Logical Message for Basic Type SHIPMENT_CHANGE01

Hi,
I want to use the basic type SHIPMENT_CHANGE01 in order to update a shipment (status, date, hour, and specifics elements) but I can't find wich Logical Message I have to use.
Could you help me please ?
Thank you
Alex

Thank you Shiva.
And do you know which Logical Message I have to use please ?
There is the SHIPMENT_CREATEFROMDATA for shipment creation but for the modification, I can't find anyone. Maybe SHPMNT (Shipping outbound) ? or SHIPPL (Inbound planned shipments) ?
Thanks again.
Alex

IDOC Exit for Basic Type PORDCR101

I had extended the idoc type PORDCR101( Create Purchase Order ) and added the new segment under E1BPMEPOITEM .
Now i want to find the exit which will help me in populating the added segment fields when the IDOC is posted .
Any sort of help is appreciated .
Regards,
Praveen.

Hello,
The message PORDCR will use FM IDOC_INPUT_PORDCR and further processing is done using a BAPI: BAPI_PO_CREATE.
Enhancement SAPLMEWP deals with the Exits related to the BAPI.
Hope the above point helps you.
Best Regards, Murugesh AS

Begin date in idoc segment E1BEN07 basic type BENEFIT3 health plan IDOC

I run tcode HRBEN0052, Idoc Data Transfer, for my health plans. If my new health plan record (IT0167) does not have a change in the General plan data (plan type, benefit plan, health plan option, dependent coverage) the begin date value on segment E1BEN07 is not the begin date for the current IT0167 record but of the previous record where the general plan data is the same. This causes a problem because the additional provider field (PROVI) value in the idoc is from the previous IT0167 record and not the current IT0167 record.
Does anyone know why the current IT0167 begin date value is not included in the idoc when there are past IT0167 with the same general plan data?

Per SAP
+The current functionality is to combine multiple continuous records if
there is no difference in the records except the dates. If you want the
functionality to be different, you can try the following.
Inside the function module HR_BEN_IDOC_SEND, there is a call to
subroutine "fill_idoc_for_period"
Kindly change the call inside the subroutine "fill_idoc_for_period"
From
1. Read Plan Data
IF idoc_categ-healt = true.
PERFORM read_infty_health TABLES it0167
error_tab
USING subscriber
begda
endda
true
reaction
CHANGING subrc.
To
1. Read Plan Data
IF idoc_categ-healt = true.
PERFORM read_infty_health TABLES it0167
error_tab
USING subscriber
begda
endda
false
reaction
CHANGING subrc.
Please note however that this is a change in the standard and thus will
be considered consulting if an error occurs, which is not supported
by our services.+

Duplicate IDOC created for basic type PEXR2002

Hi,
We are using PEXR2002 idoc for some document postings in FI. For a segment EIEDP02, when trying to write a BELNR field value which exceeds its size of CHAR 35. Its creating a duplicate segment with same key value. Because of this, the idoc not getting created and ends up in error.
Could you please anyone help me in this regard?
Thanks and Regards,
Vimala P

Hi,
In our process, the EIEDP02-BELNR value is actually filled with document text field value which is of length more than 35. What is happening right now is, if the length of document text having more than 35 characters and then with first 35 character of BELNR value one segment is created. And it again create one more segment EIEDP02 with BELNR value having the rest of the fields value(>35 characters). Thus creates duplicate segments which results in IDOC creation failure
Thanks and Regards,
Vimala P

Basic type not found

Hi Experts,
I used name for basictype 'ZMDOSTATUS' In R/3 system , now after upgrade to ECC6,while runing report to send Idoc message displayed "Basic type 'ZMDOSTAT' NOT FOUND" Last two charcher is beein truncated. How we can solve this problem without changing the name of basic type. please suggest some approch. Waiting for your reply.
Thanks :-
Ravinder Singh

hi ravendra,
can you let us know what the exact problem recently i have worked on upgradation project but i have not faced the problem what your telling . basic type 'ZMDOSTATUS' are you able to display in we31 code. if you able to do what exactly the problem .
when the upgradation every basic type will be copied to new server .
let us know the exact problem.
~linganna

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

Release? while assigning Z Message Type to a Standard SAP IDOC Basic type

Hi Experts,
Am trying to assign a custom Message Type to a Standard SAP IDOC Basic type in WE82 transaction, but am not sure How to find the Release(last column of WE82 Tx)? Pls. let me know.
Thank you

Hello,
In case of IDOC, Go to Transaction WE30, type your IDOC name & select basic type & extension.
After that select Go to -> Header data (Shift+F7), you will Idoc header info. In the same pop-up you will find IDOC release for which version.
Regards,
Sameer

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

EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

Hi,
I'm trying to various infotype 2001,2002,2006 ecc to another SAP system via ALE and since they are not part of message type "HRMD_A" I have created the extension ZHRMD_A06. I've already created the new segments(we31) and put these segments (with names Z1P2001, Z1P2002 ecc ecc) into the extension(we30). And I've assigned the extension to the message and basic type (we82).
The new segment are processed correctly in the idoc creation via transaction PFAL, but via transaction BD21 i meet the abend message : B1 070 - Internal Error : program....command... for argument Z1P2001 (for example)
In other words, BD21 do not process the custom segment but the PFAL yes...how it is possible?
I've activate the change pointer in every customizing table intersting.
Many thanks in advance for any reply
Achille

unfortunately, the standard do not provide the infotypes for the HR-TM (Time Management), that
are between the structures i must send in the other system sap.
Ok, I have never delt with Time data in HRMD_A. Probably this is the case then
Ok,now i've checked the filter in BD64 and the tables BDCP2, CDHDR and CDPOS but it seems
all correct!!
By checking Filters I mean that confirm if you have added Time Infotypes there (just
making sure). If data is appearing in BDCP2 that means there is no problem in Change
pointer creation, Just ruling out possibility.
Try with an user exit it's a good idea, but why in the PFAL the idoc (with the custom segments)
is created without problems and in the BD21 no??? This is very strange
1) Well BD21 uses the Function module (TBDME for HRMD_A) which read change pointers and
create IDOCs. So now if you have extended Segment you have to add your population code
here somewhere.
2) PFAL is Push program, my assimption here is you have wriiten some piece of code to
populate Additinal segments data here? Otherwise IDOC will not be populated
automatically.
Let me know what you think.

IDOC Message type for FB01 transaction.

Hi,
I am going to get a file which I will pass through PI (XI) and bring into IDOC and post into SAP ECC 6.0.
I just wanted to know which IDOC message type / basic type I should use for posting an FI document i.e. FB01 transaction.
Rgds

Hi,
please read SAP notes 892103 and 551035.
The correct IDOC type should be FIDCC1 / FIDCC2.
Best regards,
Andreas

Process code's function module required for the IDOC Message type PROACT

Hi,
I am trying to trigger an IDOC from ME32K transaction which will carry my Contract agreement details to XI. The IDOC I am using for this purpose is PROACT.PROACT01. But I couldn't find the outbound process code / Function module for the process code associated to this IDOC message type.
Pls help me out....
Thanks,
Ram Kalyan

I checked table EDIFCT for the message type and found this:
Function module Function type Basic type Message Type
IDOC_INPUT_PROACT F PROACT01 PROACT
Oops...I think you are looking for outbound..Ignore

IDoc : Linking Basic type and function module

Hi,
I am in the process of customizing for inbound processing.
I have one doubt reqarding below customizing :
t-code WE57:
FM                               Message type          Basic type
ZBAPI_IDOC                ACC_DOCUMENT   ACC_DOCUMENT01
ZBAPI_IDOC                ACC_DOCUMENT   ACC_DOCUMENT02
t-code WE42:
Process code     FM                                   Message type
ZBAPI                ZBAPI_IDOC                    ACC_DOCUMENT
So in this scenario, which Basic type would be considered? or if I want the Idoc with basic type ACC_DOCUMENT02, then how should be the customizing?
Thanks ,
Yogita

Hi Yogita,
The basic type depends on the version of system in consideration.
lets say for eg. HRMD_ABA has basic type from HRMD_ABA01 to 05 and they are depend on the version of the system as which to use.
Regards,
Atish

Idoc Message type & Basic type

Similar Messages

Maybe you are looking for