IDOC PO Type

Hi
Is there a way by which we can differentiate IDOC coming through EDI or FAX via a third party system?? let me know
Also can we differentiate an IDOC based on PO TYPE??
Thanks

1) First question: Yes there is the way.
Go to Header Sales order>Purchase order data>Purchase order type-->
You can add what ever PO type say
For YEDI-->For EDI.
For Manual and Fax-->DFUE.
If EDI it is EDI Order
map E1EDK14-->"13" PO Type to YEDI(If length is not suffiecient then assign number)
and later maintain this number in table and in user exit look up number and assign number to YEDI.
You can use exit EXIT_SAPLVEDA_001 for lookup. I think mostly not needed.
Also can we differentiate an IDOC based on PO TYPE??
I am not sure exactly what you mean.
For fax order is automatically posted or manual entry ?
"Reward point if usefull"
Thanks,
Narayan

Similar Messages

  • How to change the default IDOC basic type from CREMAS05 to CREMAS04.

    Hi All,
    How to change the default IDOC basic type from CREMAS05 to CREMAS04 when sending Vendor Master Data.
    When I generate partner profile, the system will add the latest version of IDOC type which is CREMAS05 to the Outbound message. In my project, I'm asked to use CREMAS04.
    I want to use BD14 to send master data directly, but the program will generate IDOC using CREMAS05. Is there a way that I can change it to CREMAS04? And also for using Change Pointers, I want to use the report RBDMIDOC, but i have the same problem.
    Thanks
    Sai Krishna

    execute WE20 and edit the outbound parameters
    here is a pretty good example: http://documentation.softwareag.com/webmethods/sapr3_gateway/sap231/pages/sapdist.htm
    Edited by: Jürgen L. on Sep 7, 2011 9:49 PM

  • IDOC message type for "Site" in SAP Retail module?

    Hi All,
    We have the need to transfer master data (through master data change pointers) of Retail Sites within the SAP Retail module (transaction:  WB01, WB02).  Does anyone know if there's an IDOC message/type already associated with this?  Thanks in advance for your help!
    Cheers,
    Matt

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

  • Problem with creation of IDOC Segment Type

    Hi,
    I tried to create IDOC Segment Type Z1LFA1 but error
    prompted "Structure Z1LFA1 already exist.".
    I tried deleting it at se11  but prompted
    "You cannot edit object R3TR TABL Z1LFA1 with the
    standard editor"                          
    and at sm30-TADIR, but prompted
    with "Cannot delete object directory entry, object exists."
    How will go about this??
    Please help!
    Thanks!

    hi,
    yup, tried doing that on we31 but the segment does not exist yet.
    we're currently upgrading from 4.6 to ecc, I think the structure
    was tranferred to our ecc client but the idoc segment and idoc type were not. I'll just have to transport it then.
    Thanks!

  • Idoc partner type LI to File Scenario.

    Hello Experts .
    I have the following scenario.
    IDOC partner type LI to xml (file).
    So we are not atlking about logical system here and we may have to use parties.
    But I am not sure as to how to go about this approach.
    For now we have Idoc coming into XI but failing after that .(Outbinding) error in reciver agreement (not to be confused with a cache issue .).
    But I understand it is because of the parties not defined properly.
    So I have defined a party and assigned my ECC system to the same.File was basically a service.Do I need to define another party for it or several other identifier
    Tried to follow How Tou2026
    Sample IDoc-XI
    Scenarios  document but it is to confusing.
    Kindly help

    Thanks for your reply.
    Well I have already tried this approach.
    That is
    Created a party :Sender_party.
    Identifiers :
    <sapid><client>   :*ALE#LI*  :<venderno>   actually ALE#LI #LF "otherwise I end up with party service not found.
    Receiver determination:
    sender party
    <BS/service> i.e. <sapid><client>     to  mail_service (for testing to see if I recieve a payload)
    <interface>
    <urn>
    Interafce determination
    sender party
    <BS/service> i.e. <sapid><client>     amd   <interface>  interface mapping
    <urn>
    Reciever agreement.
    mail_service  : reciever mail adapter.
    Error recieved.
    <!--  Technical Routing
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_NOT_FOUND</SAP:Code>
      <SAP:P1>-DMGCLNT400</SAP:P1>
      <SAP:P2>Sender_Party-,urn:sap-com:document:sap:idoc:messages.Z_DELL_PO.ORDERS05.Z_DELL_POX</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>No receiver agreement found for sender -DMGCLNT400 to receiver Sender_Party-,urn:sap-com:document:sap:idoc:messages.Z_DELL_PO.ORDERS05.Z_DELL_POX</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Kindly note nothing is wrong with cache .
    It is strange DMGCLNT400  is already assigned to the party . .

  • Idoc Msg Type COND_A in MM condition transfer

    Hi,
    Idoc message type COND_A is used to transfer condition records from one client to another using ALE.We can use t-code MEK3 to transfer PB00 condition type .
    Can anyone tell me which t-code is used to transfer condition types other than PB00 like FRA1,etc. in MM using message type COND_A?
    Thanks,
    Kaveri

    Hi,
        Pricing condition  related table is A000 and to sending this data throug ALE process transaction is VK13. Go to  transaction VK13 and click on "Condition information" then it will ask you for inputs. Then click on "Execute"...You would get the COND_A IDocs.
    Thanks,
    Asit Purbey.

  • IDOCs (Multiple Types) Collection in BPM---string index out of range

    Hi
    I am following this weblog
    IDOCs (Multiple Types) Collection in BPM
    1.
    In Step 4
    Below mapping is for N:1 transformation. (Here input will be having three different types of Abstract IDOCs and target will be having Abstract Target File type)
    (iv) MM_ISU_UKGAS_NOM_to_NOM_ABS"
    when I tried to 3 idoc as sender and My Message Type as the receiver
    I am getting the following error message
    String index out of range: 0
    so how can I do this message Mapping
    2.
    and in Step 3.
    I have just mapped
    Source Idoc 1 with Source Idoc 1
    Source Idoc 2 with Source Idoc 2
    Source Idoc 3 with Source Idoc 3
    is it right way ?
    thanks
    manian
    Edited by: manian on Dec 8, 2008 10:49 AM

    Manian,
    Multiline option should be on for receiver message .
    Mapping seems to be o.k.
    Regards,

  • 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

  • How to get the segment  detials of IDoc message type.

    Dear Friends,
    I  want to write function module , which takes the IDOC  message type  as an input and returns all the segment fields in response.
    Basically I want to get the XML schema of a IDOC message type and need to expose these details toa 3rd party application to use.
    Dear experts ,Please do give me some ideas how to achieve this .
    like tables from where i can get these details or u feel any other goos way of doing the same.
    thx,
    jeevan

    Hello experts,
    Please participate .........
    To redefine my objective I will say:--
    I am trying to do some thing very similar that is there in XI .
    You might have seen the way IDOCs are shown while mapping an idoc structure.
    Its like you select a message type and u get all the list of  Idoc Structure shown .
    I am really relying on you people.
    thx ,
    jeevan

  • Find Idoc extension type for Basic Idoc type

    Hi all,
    Is there any way to find existing extesions for Idoc given by SAP? For example, for basic idoc DEBMAS05 for version 4.7 , Idoc extension is DEBMASEXT.
    In similar way I want to know what is Idoc extension for Idoc basic type PREQCR02 [Create Purchase Requisition].
    Thanks in advance.
    Madhura

    The reason is preqcr02 is a generated idoc type  and matmas05 and debmas05 are not generated idoc types .
    You can search in table EDBAS for this .  If you go for dynamic debuggin , message comes from form
    create_ext_structure  in include MSED5F02 
    data: l_edbas type edbas.
      select single * from edbas into l_edbas
         where idoctyp eq edi_iapi01-idoctyp.
    if l_edbas-generated eq 'X'.
       message e099(b1) with
          'Action is not possible for generated idoctypes'.
    endif.
    Edited by: anil sasidharan on Feb 25, 2009 12:51 PM
    Edited by: anil sasidharan on Feb 25, 2009 12:59 PM

  • Problems with PROOF field in idoc (message type HRMD_A)

    Hello,
    I'm using the standard message type HRMD_A with IDOC base type HRMD_A06 and the function module IDOC_INPUT_HRMD.
    I have a doubt with field 'PROOF' when I fill the IDOC. Does anybody know for what is it used? For example, what's going to happen if I put PROOF = 'X' in an update operation?
    In my case I have tested that when PROOF = 'X', I receive the following warning in intotype 0001:
        The EMPLOYEE_ORG_ASSIGNMENT-ADMINISTRATOR_GROUP field is not maintainable in dialog, so it is ignored
        The EMPLOYEE_ORG_ASSIGNMENT-ORG_UNIT field is not maintainable in dialog, so it is ignored
        The EMPLOYEE_ORG_ASSIGNMENT-COSTCENTER field is not maintainable in dialog, so it is ignored
    but I cannot be sure if these warnings are due to PROFF.
    In the change data record screen, I have filled the following fields: plan version ('01'), object type ('P'), object id (employee number), PROOF ('X'), Operation ('U'). Structure for the idoc is EDIDC->E1PLOGI->E1PITYP.
    Any help on this?

    Hello,
    I'm using the standard message type HRMD_A with IDOC base type HRMD_A06 and the function module IDOC_INPUT_HRMD.
    I have a doubt with field 'PROOF' when I fill the IDOC. Does anybody know for what is it used? For example, what's going to happen if I put PROOF = 'X' in an update operation?
    In my case I have tested that when PROOF = 'X', I receive the following warning in intotype 0001:
        The EMPLOYEE_ORG_ASSIGNMENT-ADMINISTRATOR_GROUP field is not maintainable in dialog, so it is ignored
        The EMPLOYEE_ORG_ASSIGNMENT-ORG_UNIT field is not maintainable in dialog, so it is ignored
        The EMPLOYEE_ORG_ASSIGNMENT-COSTCENTER field is not maintainable in dialog, so it is ignored
    but I cannot be sure if these warnings are due to PROFF.
    In the change data record screen, I have filled the following fields: plan version ('01'), object type ('P'), object id (employee number), PROOF ('X'), Operation ('U'). Structure for the idoc is EDIDC->E1PLOGI->E1PITYP.
    Any help on this?

  • Idoc/message type related to su01 tcode fields?

    hi experts,
    when i create a user in su01,an idoc should get triggered.
    are there any standard idoc / message type having fields related to this.
    thanks,
    charu
    Edited by: charudevrani on Jan 11, 2012 7:38 AM

    Hi Charu,
    You can use one of following IDoc types, depending on the action you want to perform on the user master record:
    USERCHANGE     Change user
    USERCLONE     Create User with Template in Another System
    USERCREATE     BAPI to Create a User
    Regards,
    Marcin

  • CRM: IDOC Message Type: CRMXIF_PARTNER_REL_SAVE_M

    Hi,
    I'm currently working on a CRM data migration project. I'm using the IDOC Message Type: <b>CRMXIF_PARTNER_REL_SAVE_M</b> to map data into contact relationship structures.
    The problem I am having is the above interface works with SAP standard <b>BUR001</b> type contact relationships. But a copy was taken of <b>BUR001(is contact person for) => ZUR001 (former contact person of)</b>. This allows you to add a date range: <b>DATE_TO - DATE_FROM</b>. Using the above interface I am able to map these dates to the <b>ZUR001</b> type relationships.
    All the other data I try and map  i.e Function, Telephone No, Fax No ect.. will not map. I'm at a loss as to why not?
    note: running CRM 4.0
    Any help with this would be greatly appreciated.
    Regards,
        Philip Johannesen

    Thanks Saquib, the OSS note was very informative.
    Do you know where I can find <b>" In addition, you can find DXWB/LSMW examples under service.sap.com/CRM-Integration which you can install in a CRM system and use as models."?</b>
    I've looked under the new link <b>"service.sap.com/crm-netweaver"</b>. But have been unable to find any examples.
    I've awarded points as promised.
    Regards,
       Philip Johannesen

  • Equivalent Idoc message type for EDIFACT BANSTA

    Hi Experts,
    I am trying to find out the equivalent IDOC message type for EDIFACT BANSTA. The purpose of the message is to show the item level statuses for a particular payment batch. There are lot of references about FINSTA01, however, this is for account level status response.
    If anybody know the equivalent idoc message type for EDIFACT BANSTA, kindly let me know.
    Thanks in advance.
    Regards,
    Ravi

    Thanks raja shekar. I posted this thread in ABAP development forum.

  • Posting multiple idocs of different IDOC/message type

    Hi! ALL
    It would be very helpful if you please provide your valuable suggestions...
    I have 4 different file to IDOC mappings and i am trying to post all the 4 using the same interface determination....out of the 4 ....2 IDOC are of the same message type...this is throwing out an error...
    <SAP:Code area="IF_DETERMINATION">CX_ID_PLSRV</SAP:Code>
      <SAP:P1>Inbound interface was found more than once (for same sender and receiver) for outbound interface http://ck.com/xi_com/Ship.MI_SHIP</SAP:P1>
      <SAP:P2 />
    I am trying to use 3 File IDOC mappings in the same Interface determination, for example has the following inbound receivers in the interface determination:
    DESADV
    WMMBXY
    DESADV.........I am using DESADV twice as the Message Mapping is different for each of the inbound DESADV idoc
    Please, let me know...if you were able to post similar message type IDOC in the same inteface determination.
    Your help is greatly appreciated....
    Thank you,
    Patrick
    Thank you

    Hi! Bill
    I am using 3 message interface(in 1 interface determination) and i am able to post 3 idocs....the problem only arises when the 4th idoc is of the same message type as any of the first 3.
    I am trying to exclude the 4th mapping.....b'cos the issue with similar message/idoc's type issue.....but incase u have a solution let me know...here is an example
    Eg:
    DESADV
    WMMBXY
    SHIP...is posting fine!!
    But...problem with..posting...
    DESADV
    WMMBXY
    SHIP
    DESADV(4th same as first)
    And again as mentioned...each have there own message mapping(MI) and interface mapping(IM)....and are in the same interface determination...as outbound interface and BS is the same for and in the inbound as u know is IDOC..R3.
    Thank you for your response....
    Patrick

  • IDOC Message Type FIDCCP02 - Error RW029

    Hi All,
    We are trying to post a FB01 using a IDOC message type - FIDCC2 and struck at error message -
    <b>Accounting transaction not permitted for posting in FI/CO
    Message no. RW029</b>
    When i try to post directly using the exact data in the IDOC, through FB01, there is no problem.
    Debug showed that the error is in the following -
    Include <b>LRWCLF01</b>
    check business process
    SELECT SINGLE * FROM t022 INTO ld_t022
    WHERE activity = t_acchd-glvor.
    IF sy-subrc IS INITIAL.
    IF LD_T022-VORGTYP = 0 OR  <---------
    IF ld_t022-satztyp <> 0.
    MESSAGE e029 WITH t_acchd-glvor.
    ENDIF.
    ELSE.
    MESSAGE e029 WITH t_acchd-glvor.
    ENDIF.
    If this is not the right message type to use, can you suggest any other message type? FB01 we are trying to post is a simple GL posting, no tax, no withholding, etc. IDOC is just a 2 line posting.
    Any help/advice is highly appreciated.
    Many Thanks,
    Shashi

    Hi Shashi ,
                      This table is for Business Process t022 based on activity .
    Check your customise settings .
    There is no problem with message type .
    Please reward if useful

Maybe you are looking for