Userexit for extended idoc for std. idoc WMMBID02 for T.Code MB1A & MB1B

Hi,
Which userexit we have to use to populate values in to extended idoc fields of the standard inbound idoc WMMBID02?
Pls share ur experience.
Thanks & Regards,
Balaji

Hello using this you can find out used user exit
1.From SE93 get the program name corresponding to the transaction.
2. then se38 - > enter program name -> attribute -> display
3. Get the package from here.
4.  Go to SMOD . Do f4 on enhancement -> information system. enter your package here
5. You will get the list of all the available exits for the package.
List could be a long one.Now best thing to do is to sit with your functional analyst. find out approproate exit from the description. put a break-point there. ask functional analyst to run the transaction. if transaction stops at the break point that's the exit you want

Similar Messages

  • TSV_TNEW_PAGE_ALLOC_FAILED -  No more storage space available for extending

    Hi
    Im SAP-BW Consultant. I need some code in the transfer rules. But while im loading data , im getting "No more storage space available for extending an internal table.
    Pls check my code and modify it so that i can load the data of 5,000,00 records
    TYPES: BEGIN OF tys_TG_1,
                         /BIC/ZIUTILICH           TYPE /BIC/OIZIUTILICH,
                       /BIC/ZIRGRCH           TYPE  /BIC/OIZIRGRCH,
                       /BIC/ZPRODUCT           TYPE /BIC/OIZPRODUCT,
    END   OF tys_TG_1.
    TYPES:  tyt_TG_1        TYPE STANDARD TABLE OF tys_TG_1
                                                     WITH NON-UNIQUE DEFAULT KEY.
    data: e_s_result type tys_TG_1.
    data: e_t_result type tyt_TG_1.
    DATA : ITAB1 TYPE STANDARD TABLE OF  /BIC/AZDSO_HYD00.
    DATA : WA_ITAB TYPE /BIC/AZDSO_HYD00.
    loop at RESULT_PACKAGE into e_s_result.
         Select /BIC/ZIUTILICH /BIC/ZIRGRCH /BIC/ZPRODUCT                                               FROM       /BIC/AZDSO_HYD00 INTO
                                    (e_s_result-/BIC/ZIUTILICH,
                                    e_s_result-/BIC/ZIRGRCH,
                                     e_s_result-/BIC/ZPRODUCT)
                                 WHERE
                                 COMP_CODE = e_s_result-COMP_CODE AND
                                 PROFIT_CTR = e_s_result-PROFIT_CTR .
              append e_s_result to e_t_result.
         endselect.
             clear e_s_result.
    ENDLOOP.
    refresh RESULT_PACKAGE.
    move e_t_result[] to RESULT_PACKAGE[].
    So im getting TSV_TNEW_PAGE_ALLOC_FAILED -  No more storage space available for extending an internal table..
    I think there is a problem in the code. pls look it and modify it.
    Regards
    kumar

    Hello Kumar,
    The amount of data you can store in an internal table is limited by the width of the table together with the available memory on your machine. If you try to put too much data in your table you'll always get that problem.
    As I see it you have a table RESULT_PACKAGE with some fields and based on the entries in that table you select one row out of another table.
    You can easily use
    Select
    /BIC/ZIUTILICH /BIC/ZIRGRCH
    /BIC/ZPRODUCT FROM
    /BIC/AZDSO_HYD00
    INTO TABLE e_t_result
    FOR ALL ENTRIES in RESULT_PACKAGE
    COMP_CODE = RESULT_PACKAGE-COMP_CODE AND
    PROFIT_CTR = RESULT_PACKAGE-PROFIT_CTR .
    That still doesn't solve your memory problem hence you should try to process the data in packages, because you obviously don't have enough memory to process all data at once.
    You can add the following:
    Select
    /BIC/ZIUTILICH /BIC/ZIRGRCH
    /BIC/ZPRODUCT FROM
    /BIC/AZDSO_HYD00
    INTO TABLE e_t_result
    PACKAGE SIZE xxxx
    FOR ALL ENTRIES in RESULT_PACKAGE
    COMP_CODE = RESULT_PACKAGE-COMP_CODE AND
    PROFIT_CTR = RESULT_PACKAGE-PROFIT_CTR .
    PROCESS your data here
    ENDSELECT.
    You might also want to discuss the issue with your basis team if there is a way to get more memory if there is no way to do that process.
    Hope that helps,
    Michael

  • Creation of  New Message Type for Extended IDoc

    Dear Friends,
    I want to create New Message Type for MATMAS and want to Active Change Pointers accordingly. Thru this Message Type how can I able to use Extended IDoc which I have created for Basic Idoc Type MATMAS05.
    I am Sending Data from SAP to XI ; Any one can help me in this How can I create the Message Type with the IDoc Extn .
    for Change Pointers.
    Warm Regards,
    Naveen Mutyapu.

    Hi naveen mutyapu,
    see these links
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    http://www.allinterview.com/rss/interview-questions/new/SAP-ALE-IDocs.xml
    happy learning.
    thanks
    karthik

  • IDOC WMMBID02 for Outbound

    Hi,
    I am trying to configure an outbound IDOC for GI/ GR. I was told to use WMMBID02 for this,  but it uses FM L_IDOC_INPUT_WMMBXY.
    Has anyone tried to use IDOC WMMBID02 for outbound? I want to use this for a particular GI with Material Document as a parameter.
    Thanks.
    Kenny

    Hi Ferry,
    Thanks for the reply.
    I cant seem to make this test program work. I just put the Mat Doc Num and the Year then ticked direct processing. It then shows "Check your entries".
    Please help.
    Thanks.
    Kenny

  • Process code for extended idoc

    Hi,
    If we are creating an extended idoc, do we have to assign a new process code to it ?
    Or will the process code and the associated function module for the basic type work as well for the extended idoc ?

    Process code will come in to picture when you deal with IDOCS .. you need to assign a code which internally will have a Function module or a Include, that will have entire code to run your bussiness for an IDOC or EDI or ALE.
    Process Code is a different name for specific purposes like function module. IDocs are written in this process.
    Outbound Process Code - if you are using outbound processing under Message Control, the IDoc is generated in the IDoc Interface. The process code names the relevant function module
    Inbound Process Code - names the function module or workflow which reads the IDoc data and transfers the data to the application document.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/content.htm
    Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
    Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
    Click on Create new and enter a description and press enter.
    Click on ZIDOCTYPE01 and then on the Create icon.
    Enter ZIDOCTYPE as the segment type, click on Segment Editor.
    Enter a description for your segment type and create.
    Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
    Save and generate, press back
    To release the segment choose Goto, Release from the menu.
    Check the box on the line of your segment.
    Save, back and enter.
    Your Idoc type structure should be displayed with your new segment.
    Save and back.
    To release the Idoc type choose Extras, Release type from the menu and Yes.
    Reward points if useful.

  • Change pointer for Extended IDOC

    Hi guys,
    I have Extended a standard IDOC MATMAS and added few additional fields into it.
    Now i have make Change pointers enabled for this IDOC extension.
    Is it possible?
    Can some one guide me as to how can i create Change pointers for EXTENDED IDOC?
    any extra steps required?
    Sahil

    Hi,
    you can use BD52 transaction to add the extended idoc fields inorder to activite the change pointers for them.
    Please note that the fields in the extended idoc should have chnage entry in CDHDR whenever you change the field in MM02 transaction. if not change pointer will not work.
    If these fields are not marked in change entry in MM02 transaction you can use user exit while saving MM02 and then create the change document for them by coding inside those user exit.
    Hope it helps,
    Shanmugavel chandrasekaran.

  • How to write the logic for extending Idocs...

    Hi,
          Can anybody pls explain how to write the logic for extending IDOCs with an example...
          Good suggestions can be appreciated..
    Regards,
    Ram

    Hi Ram,
    Generally the IDoc user exit is called at the following places:
      1) When the control record is read.
      2) After each and every segment in the data record
      3) At the end of the data segment processing.
    The IDoc user exit interface generally imports IDOC_DATA (data record internal table) table. Now the data records in the internal table should appear in the same order as maintained while defining IDoc structure (WE30 transaction). For SAP standard segment SAP code will take care of this. For extended segment you will have to take care of this aspect by appending the Z-segment in the IDOC_DATA table.
    You can do this by:
             looping at IDOC_DATA table:
                 - Do a case-endcase fo IDOC_DATA-SEGNAM (This stores the segment 
                   structure as per the hierarchy).
                 - Within the case for "Z-segment" you can write the logic for appending
                   the Z-segment to IDOC_DATA-SDATA.
    Hope this gives some clue.
    Regards,
    Gajendra.

  • User exit for extending iDoc

    Hi gurus,
    Can anyone tell me the user exit for extending the message type COAMAS.
    Thanks & Regards,
    Soumya.

    Exit name Short text
      SIDOC001  Customer function for module pool EDI1
      SIDOC002  CA-EDI: Exits in Function Group EDI6 (Partner Profile)

  • IDOCs creation - Transfer Orders(TOs)  for Deliveries - Basic doubts, thanq

    Hi Experts,
    Am new to IDOCs.  I hv a requirement, so, request u that, Can I get some Wht to do tips from u?
    My doubts:
    1- I hv been asked to create IDOC, Wht does it mean?
    2 - How the created IDOC will be get posted?
    My requirement is:
    Original inbound idoc sent from Gentran will update the delivery with all serial numbers per material for all serialized product.  The message code will be the indicator that a Transfer Order-TO, idoc must be created for TO confirmation.
    I need to do===>   Should be executed only when the message code on the delivery idoc is u201CTOCu201D.  Look up the warehouse code on the delivery header using the delivery nbr in the delivery idoc.  Create a new TO confirm idoc per delivery idoc being processed.  Create a line item on this idoc for every line on the delivery idoc.  Each TO line includes the delivery number and delivery item number so the TO number and line number can be looked up in table LTAP by using the delivery number and line item number found on the delivery idoc.  There will be at 2 transfer orders for each delivery item b/c of the 2 step pick process, so select the TO nbr that has 916 as the destination storage type (LTAP-NLTYP).  There may be more than 1 pair of TOs per delivery item so this must be completed for each TO found relevant to each delivery item.
    The inbound delvry03 idoc will update the delivery with the serial numbers as part of the standard functionality.  Since the transfer order must also be confirmed with the quantities on the inbound idoc, an additional idoc must be created from within the delivery update process.  The transfer order can be updated and confirmed using the standard idoc and function module which should be created and initiated from the delivery update function module customer exit.
    Source = DELVRY03     Destination = WMTCID01
    Record Name-Field Name-Record Name-Field Name-Description---Comments
    E1EDL20     VBELN-E1LTCOH-LGNUM-Warehouse Number-Look w/ idoc delivery nbr
    E1EDL20     VBELN-E1LTCOH-TANUM-Transfer Order Number- Look w/ idoc delivery nbr
    E1EDL24     POSNR-E1LTCOI-TAPOS-Transfer Order Line Item- Look  w/ idoc delivery line nbr
    EVERY THING IS DATA TRIGGERED!!!
    thanq
    Edited by: Srinivas on Jun 27, 2008 4:41 PM

    IDOC Programming
    There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
    NEED FOR ABAP PROGRAMMING arises if
    1)New IDOC was created
    Depending upon the triggering mechanism i.e change pointer,message control
    etc the programming technique changes and the type of process.
    2)Existing IDOC was extended
    User Exits are used to populate data in new segments added and to read them
    back.
    3)To enhance an exsiting process.
    User Exits are used .
    Basic structure of an OUTBOUND PROGRAM
    The basic structure of all outbound programs is same. The CONTROL
    record which is of TYPE EDIDC has to be filled. It contains important fields like
    IDOCTP IDOC type
    MESTYP Message Type
    RCVPRN Recieving Partner (Destination)
    RCVPRT Partner Type (it is LS i.e Logical System)
    The DATA RECORD internal table which is of TYPE EDIDD has to be filled
    in the same order as there are segments in the IDOC definition.
    It has 2 important fields which are to be filled ,these are
    SEGNAM Name of the segment
    SEGDATA Data in the segment and can be upto 1000 bytes.This field
    is corresponds to each data segment in the IDOC.
    e.g.
    DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
    DATA W_SEGDATA LIKE zsegment "custom segment zsegment
    INT_EDIDD-SEGNAM = 'ZSEGMENT'
    W_SEGDATA-field1 = value "taken from some table
    W_SEGDATA-field2 = value "taken from some table
    INT_EDIDD-SEGDATA = W_SEGDATA
    APPEND INT_EDIDD
    This will fill the data record corresponding to the segment ZSEGMENT . For all
    segments the sam steps will be repeated until all the data corresponding to all the
    segments in the idoc is filled in the internal table of type EDIDD.
    There is only one control record and can be multile data records in the idoc
    structure.
    Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
    In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
    OUTBOUND PROCESS AND OUTBOUND PROGRAM.
    Outbound programs are used in outbound process to genearte IDOCs . There
    purpose is to extract the data from the tables and to fill the IDOC data records
    and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
    Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
    1)Message control
    Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
    In outbound programs(function module) that use message control the key of the
    application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
    message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
    The parameteers passed to the function module are
    IMPORTING PARAMETERS
    OBJECT LIKE NAST
    It contains documents key.
    CONTROL_RECORD_IN LIKE EDIDC
    It contains the partailly filled control record
    EXPORETING PARAMETER
    OBJECT_TYPE
    CONTROL_RECORD_OUT LIKE EDIDC
    TABLES
    INT_EDID LIKE EDIDD
    The internal table used to fill the data records in the same order as they exists in the IDOC.
    The important parameters that should be filled in the custom function module are
    CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
    2)Stand alone programs
    Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
    Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
    Data is filled in an internal table of TYPE EDIDD according to segment definitions
    and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
    3)Change pointer
    Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
    ALE/IDOC Transaction
    SALE Area Menu for ALE configurations.It includes transactions for
    Logical System definition and linking it to a client, Transactions for
    RFC Destination and Port Definition Etc.
    SM59 RFC Destination
    Here we specify the login settings for the destination including
    the I.P address or Application Server name and the User name and
    password.The information entered here is used to run Remote Function
    Calls(RFC ) on the destination server .We can create number of types
    of RFC Destinations but 3 types are important .
    R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
    The name of the RFC destination should be same as that of Logical
    System as it helps in creation of automatic partner profiles.
    WE21 Port Definition.
    There are 6 types of ports but only 2 types File and Transactional RFC
    types of ports are important.
    We have to specify the RFC Destination before a port can be created.
    WE57 This is used to assign the Inbound function module to the Message Type
    and to the IDOC Type.
    WE42 This is used to define the process Code for Inbound Processing.
    BD95 Define Filter object type .We can specify the field and the table it belongs
    to as a filter object .
    BD59 Assignment of Filter object type to the Message Type .Here we create the
    link between Filter object and the segment and the message type and the
    segment Field.
    BD50 Set message Type to reducible.
    BD65 Define Mandatory Fields.
    BD64 Distribution Model . Also known as Customer Distribution Model Used to
    define all the messages that will be exchanged between remote systems
    and the name of thes logical systems. Any filters can also be specified.
    The model once created has to be distributed on every system which will
    be communicating ,It can be maintained on only One system.
    BD21 Creating IDOcs from change pointers.
    This can be used to create IDOCs from change pointers for a particular
    message LIKE MATMAS.
    BD22 This can be used to delete change pointers.
    BD87 Status Monitor. Idocs can be selected base on number of criteria and there
    processing status can be seen in detail.
    BD10 Material Master Data Distribution .
    Based on Message MATMAS.
    BD12 Customer Master Data Distribution .
    Based on Message CREMAS.
    BD14 Vendor Master Data Distribution
    Based on Message DEBMAS .
    BDFG Generate ALE Interface for BAPI.
    Here we specify the Business Object and the BAPI Function module for
    which the interface has to be created.
    WE31 Segment Editor.
    This is used to create segments. We create the segment type and
    segment definition is automatically created by editor e.g. Z1DUMMY is
    segment type and Z2DUMMY is the segment definition .We specify the
    fields and the data elements these cp\orresponds to create segments.
    WE30 IDOC Editor
    It is used to create a new IDOC Type or IDOC Extension .We specify the
    segments that will be addd to the IDOC type.
    WE02/05 IDOC List.
    Various selct options and parameters are provided to select IDOCs
    depending on the date, direction , mesage type etc.
    WE20 Partner Profile
    Here we create partner profile for each and every partner from / to which
    the messages will be exchanged.There are 6 types of PF generally only
    profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
    We specify the partner number and partner type and the agent and
    the agent type responsible for handling of errors .
    For every message send to the partner we have a outbound record and for
    evry message coming from the partner we have the inbound record .
    We specify the message in the otbound/inbound records ,double
    clicking will take us to the detailed screen where the IDOC Type ,Port
    and whether the IDCO will be immediatelt processed or collected are
    mentioned.

  • Idoc type and message type for Planned Independent Requirement (PIR)

    Hi
    Can anyone please give me the information on the idoc type and message type for Planned Independent Requirement(PIR)?
    And also the prerequisites to use them.
    Regards,
    Lohitha
    Moderator message: please do more research before asking, show what you have done yourself when asking.
    Edited by: Thomas Zloch on May 23, 2011 10:45 AM

    Hi,
    You can use IDoc type WMMBID02 with message type WMMBXY.
    Also please check test program RLMBXY00 to simulate IDoc WMMBID02.
    Regards,
    Ferry Lianto

  • Idoc type and message type for inventory

    Hi All
    What is the idoc type and message type for inventory adjustments? Thanks for any help
    Thanks
    Ricky

    Hi,
    You can use IDoc type WMMBID02 with message type WMMBXY.
    Also please check test program RLMBXY00 to simulate IDoc WMMBID02.
    Regards,
    Ferry Lianto

  • Problem when setting Reason of Rejection for a sales order using IDOC

    Hi All,
          I am working on a requirement where i need to put a reason for rejection as 'Item Cancelled' for a sales order via IDOC 'IDOC_INPUT_ORDCHG' in a third party scenerio where the PR is created automatically from the sales order . When the IDOC is run in the foreground I get the information message Subsequent function  " 'Purchase requisition from sales document' not possible Item & was rejected "(Message V1579) and the IDOC results in a error when run  in the background mode because of the same information message. The message should not appear when a sales order is being processed in the background but still the message is being displayed . Is there any way the message can be suppressed ? Thanks in Advance.
    Regards,
    Sowmya.

    can you send the program how you create a so or po using IDOC, as i've a assignment creating PO using IDOC & then creating a sales order of the PO. and i dont know how to create a IDOC. SO IF you have sample program it would be help full
    Thanxs

  • XI Business content for MDM - Syntax error in IDOC adapter

    Hi mates,
    I'm trying out the Master Data Harmonization scenario for Vendor data with R/3 as the client system. I'm using SAP delivered XI Business content for MDM. The mapping program is generating ADRMAS and CREMAS IDocs but the IDOC adapter reports that there is a syntax error in ADRMAS IDOC. Find below the details.
    <i><SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:Stack>
      <SAP:Retry>M</SAP:Retry></i>
    Generated ADRMAS IDOC is
    <i>  <?xml version="1.0" encoding="utf 8" ?>
      <ADRMAS02>
      <IDOC BEGIN="1">
      <EDI_DC40 SEGMENT="1" />
      <E1ADRMAS>
      <OBJ_TYPE>LFA1</OBJ_TYPE>
      <OBJ_ID>0000500140</OBJ_ID>
      <CONTEXT>0001</CONTEXT>
      <E1BPAD1VL SEGMENT="1">
      <FROM_DATE>00010101</FROM_DATE>
      <TO_DATE>99991231</TO_DATE>
      <NAME>Swift Transportation</NAME>
      <COUNTRY>US</COUNTRY>
      <COUNTRYISO>US</COUNTRYISO>
      <LANGU>E</LANGU>
      <LANGU_ISO>EN</LANGU_ISO>
      <SORT1>SWIFT TRANSPORTATION</SORT1>
      <TIME_ZONE>CST</TIME_ZONE>
      <E1BPAD1VL1 SEGMENT="1">
      <LANGU_CR>E</LANGU_CR>
      <LANGUCRISO>EN</LANGUCRISO>
      <ADDR_GROUP>BP</ADDR_GROUP>
      </E1BPAD1VL1>
      </E1BPAD1VL>
      </E1ADRMAS>
      </IDOC>
      </ADRMAS02></i>
    Strangely, the control record is blank. I looked at the XSLT program, it is coded that way. I do not understand the reason. Is the error pointing to the control record?
    Look at the code sample from XSLT mapping program
      <xsl:for-each select="IDOC/*/E1ADRMAS">
           <IDOC BEGIN="1">
           <!-- The header data of each single ADRMAS-IDoc needs to be there but does not require specific data -->
                <EDI_DC40 SEGMENT="1"/>
                <xsl:apply-templates select="."/>
           </IDOC> 
      </xsl:for-each>
    How can an IDOC w/o control record be posted?
    Did anyone come across this error? Whats wrong/missing?
    I appreciate ur inputs.
    thx in adv
    praveen

    Moorthy,
    I tried reloading the IDOC metadata from IDX2. Still I get the same error.
    Regd, IDOC w/o control record, can u elaborate on "dynamic value while posting IDOCs". From where, XI message SOAP header with Business System replaced by corresponding logical system names?
    Thanks
    Praveen

  • How many types of ports are there which we use for data transfe in ale/idoc

    friends let me know how many types of ports  are there which we use for transfering
    data in ale/idocs?

    Hello,
    you can use file port,trnasactional RFC port.FI you are using IDOC-XML conversion combination,then you can XML port also.
    Thanks

  • Creating Conditions for Purchase Info Records using IDoc COND_A01

    Hi All,
    we are using IDOC COND_A01 to update and add conditions in ME12 transactions.
    But when we send a condition IDoc which contains 2 condition types (Segment KONP), the standard function call creates only one database entry in the table KONP. The entry in KONP is for  standard condition types PB00, but not  for company specific types (Say: ZABC) .But when we create them manually in ME12 maintaining an purchase info record  we get both the entries in the KONP database table.
    Has anyone come accross such a problem? Is there any special field in the IDoc COND_A01 which controls the creation of the condition types?
    Thanks for any answer!

    U should use basic type INFREC01 instead of NFRECMASS01.
    Within the FM there is a check for basic type like:
    check idoc type
        if f_idoc_control-idoctp <> c_idoctp_infrec01. " INFREC01
          raise wrong_function_called.
        endif.
    Edited by: Joyjit Ghosh on Sep 15, 2008 4:57 PM

Maybe you are looking for