Problem in Idoc extension for ORDERS05

HI all,
Am facing problem in inbound idoc, we have extended the Idoc ORDERS05 with one custom segment, and written the code in user exit EXIT_SAPLVEDA_001 and include ZXVEDU03 exit is triggering properly, sales orderis genarted successfull, but z-fileds are not updating in VBAK table,
so plz help....
Regards,
Suresh.D
Edited by: suresh dameruppula on Oct 20, 2009 2:39 PM

Hi Suresh,
The function exit and the include what you found is to read data from the IDOC segment into either internal table or structure.
That's the first step which you have done is part of the below set:-
EXIT_SAPLVEDA_001 & ZXVEDU03
Now you need to populate the which you have read from the idoc into the document for that you need to write the code in the below set. The below one is a function exit which will be called during the BDC. You can see this below
Aufruf Transaktion Auftragerfassung VA01                             *
call transaction Order Entry VA01                                    *
        CASE xaprau.
at line number 131 in the function module IDOC_INPUT_ORDERS.
EXIT_SAPLVEDA_002 & ZXVEDU04
Please let me know if you still have any further queries.
Thanks,
Mahesh.

Similar Messages

  • Problem in Idoc extension for PREQCR02

    Hi all,
    While extending Basic type PREQCR02 getting error "Action is not possible for generated Idoc types"
    Is it not possible to extend Idoc PREQCR02?
    Regards,
    Suresh.D

    Hi Suresh,
    The function exit and the include what you found is to read data from the IDOC segment into either internal table or structure.
    That's the first step which you have done is part of the below set:-
    EXIT_SAPLVEDA_001 & ZXVEDU03
    Now you need to populate the which you have read from the idoc into the document for that you need to write the code in the below set. The below one is a function exit which will be called during the BDC. You can see this below
    Aufruf Transaktion Auftragerfassung VA01                             *
    call transaction Order Entry VA01                                    *
            CASE xaprau.
    at line number 131 in the function module IDOC_INPUT_ORDERS.
    EXIT_SAPLVEDA_002 & ZXVEDU04
    Please let me know if you still have any further queries.
    Thanks,
    Mahesh.

  • IDOC EXTENSION FOR DEBCOR

    Hi gurus,
    can anyone of you please tell me step by step procedure to create an idoc extension, lets say for DEBCOR.
    Thanks,
    Rajeev

    hi rajeev...
    can u please share me the detail description of how to go for Idoc extension with an example.

  • IDOC reduction for ORDERS05

    Hi,
    Is it possible to reduce the idoc for ORDERS05? I used  BD53 and gave a new message type ZORDERS and it is asking for with reference to message type...I am not able to see orders there.
    Can anyone suggest how to proceed here?Is it something that only master idoc can be  reduced?Pls suggest.
    Regards,
    Jeyananth

    If you've just tried to enter ORDERS in there, you would've seen this message:
    "There is no data maintained in the reduction pool for message type ORDERS
    Message no. B1121
    Diagnosis
    This transaction is used for maintaining and displaying reduced message types. In the standard not all message types can be reduced.
    There is no data in the reduction tool for message type ORDERS.
    Procedure
    Use the transaction WE30 for maintaining and displaying the associated intermediate document type, or use the transaction BD60 to maintain the data for the reduction tool."
    But I wouldn't recommend reducing the IDoc - it's more trouble than it's worth IMHO.

  • IDoc extension for HRMD_A07 - Error message B1-070

    I am trying to create a custom extension to HRMD_A07 to capture some additional data added to infotype 0001.  I have gone through the WE31, WE30, WE82, SM30 transactions to create the extension but when I try to test with PFAL I am getting the message B1-070.
    Internal error: Program read table idoc_structure, command
    data_select_for_block, argument ZHR_SEG
    The extractor appears to be trying to fill in the original HRMD_A07 basic type and the HRMD_A07 with the extension.
    Any hints?
    Thanks,  Rob.

    Dear Rob,
    Although your post's date is old but I would share my knowledge for whom has the same issue.
    Last day I had the same problem and could not find any solution on internet so I had to trace the code. Fortunately I managed to fix the problem My colleagues had extended an IDOC by a segment but after that the segment was deleted so I was getting an error in ALE.
    Issue comes "DATA_SELECT_FOR_BLOCK" method which is using I_DOC_DATA table that fills in PFAL transaction. thru running PFAL IDOC data reads from table T777D.
    Go into and find the related record and clear it
    By the way after that I found http://scn.sap.com/thread/3322338 useful
    Cheers,
    Omid

  • Idoc extension for eewb custom fields for BUS20001

    Hello.
    I have an almost exact question as , but I still need to ask what I'm supposed to do.
    We've done enhancements in EEW and I can see some append structures in CRMXIF_BUSTRANS (for example). The problem is that when I generate outbound idoc the sturcture E101CRMXIF_BUSTRANS is missing the corresponding append structures.
    Why isn't EEW adding this, or do I have to generate/re-generate something?
    I've tried to Cancel release/release the ALE interface in BDFG, but with no results.
    I think the replications (initial load and delta load) to r/3 has all EEW modifications, but when it comes to idocs, it woun't change.
    Is the only solution to create a new idoc in bdfg and create a z-structure?
    The FM ALE_CRMXIF_ORDER_SAVE_M used for populating the idoc, would work if the structure E101CRMXIF_BUSTRANS was extended with the same appendstructure (since the only thing it does is a move-corresponding...).
    So, the question is if I have to create a new z-idoc, or if it's possible to regenerate the structure used in the idoc segments?
    Regards, Mikael Löwgren

    Hi,
    When you have ignored the inconsistencies, this means the complex structure fields and the corresponding Idoc Segment fields are different in the support package.
    If this is the case, when the Idoc is regenerated in Tx BDFG, you will find the message type will be in
    error when you press F9 to do the syntax check.
    There you will see the segments which are in error as well as the 'Interface is not current and it must be regenerated' error message.
    Check those segments listed in syntax check against the respective complex structure. If there are differences like if some fields are added or the data element is changed, kindly correct the segment fields via Tx IDOC.
    If you need to add fields to the segment, you need to increase the field length of the segment in EDISDEF table, which can be done in Tx IDOC --> Repair segments tab --> Change entries in EDISDEF table.
    There you can change the field length and then change the entries in EDSAPPL table.
    Similarly if you take out all the errors in the segments listed for a particular message type and try to release the Idoc, it will be released without any errors.
    This happens, as far as my understanding goes, mainly because the complex structures might under go some changes from the development side but not the Idocs. Since both are different entities, mostly these types of things happen.
    Do let me know  if this has helped you.
    Venkat

  • HRMD_A06 IDOC EXTENSION FOR INFOTYPE 0001 WHICH HAVING A ZFIELD

    hi folks,
    i am extending the idoc hrmd_a06. and in infotype 0001 we have zfield. for that z field extension is required. iam tryied with naming convention z1p0001 or ze1p0001. but it throws error from t777d table.so plz let me know how we extend it

    hi folks,
    i am extending the idoc hrmd_a06. and in infotype 0001 we have zfield. for that z field extension is required. iam tryied with naming convention z1p0001 or ze1p0001. but it throws error from t777d table.so plz let me know how we extend it

  • IDOC format for ORDERS05

    Hi all,
    I have search through the web and in sap.com and I haven´t found the specification (details of fields and their meanings) for the standart idoc ORDERS05.
    Does anyone on the forum knows where i can find this information?
    (I have no access to a SAP system).
    Thanks for all.

    Structure of basic type ORDERS05
    Purchasing/Sales
    E1EDK01 : IDoc: Document header general data
    Status: Required , min. number : 1 , max. number : 1
    Structure
    E1EDK14 : IDoc: Document Header Organizational Data
    Status: Optional , min. number : 1 , max. number : 12
    Structure
    E1EDK03 : IDoc: Document header date segment
    Status: Optional , min. number : 1 , max. number : 10
    Structure
    E1EDK04 : IDoc: Document header taxes
    Status: Optional , min. number : 1 , max. number : 10
    Structure
    E1EDK05 : IDoc: Document header conditions
    Status: Optional , min. number : 1 , max. number : 16
    Structure
    E1EDKA1 : IDoc: Document Header Partner Information
    Status: Optional , min. number : 1 , max. number : 99
    Structure
    E1EDKA3 : IDoc: Document Header Partner Information Additional Data
    Status: Optional , min. number : 1 , max. number : 99
    Structure
    E1EDK02 : IDoc: Document header reference data
    Status: Optional , min. number : 1 , max. number : 10
    Structure
    E1EDK17 : IDoc: Document Header Terms of Delivery
    Status: Optional , min. number : 1 , max. number : 4
    Structure
    E1EDK18 : IDoc: Document Header Terms of Payment
    Status: Optional , min. number : 1 , max. number : 3
    Structure
    E1EDK35 : IDoc: Document Header Additional Data
    Status: Optional , min. number : 1 , max. number : 99999
    Structure
    E1EDK36 : IDOC: Doc.header payment cards
    Status: Optional , min. number : 1 , max. number : 99
    Structure
    E1EDKT1 : IDoc: Document Header Text Identification
    Status: Optional , min. number : 1 , max. number : 99
    Structure
    E1EDKT2 : IDoc: Document Header Texts
    Status: Optional , min. number : 1 , max. number : 9999999999
    Structure
    E1EDP01 : IDoc: Document Item General Data
    Status: Optional , min. number : 1 , max. number : 999999
    Structure
    E1EDP02 : IDoc: Document Item Reference Data
    Status: Optional , min. number : 1 , max. number : 10
    Structure
    E1CUREF : CU: Reference order item / instance in configuration
    Status: Optional , min. number : 1 , max. number : 1
    Structure
    E1ADDI1 : IDoc: Additionals
    Status: Optional , min. number : 1 , max. number : 999999
    Structure
    E1EDP03 : IDoc: Document Item Date Segment
    Status: Optional , min. number : 1 , max. number : 10
    Structure
    E1EDP04 : IDoc: Document Item Taxes
    Status: Optional , min. number : 1 , max. number : 10
    Structure
    E1EDP05 : IDoc: Document Item Conditions
    Status: Optional , min. number : 1 , max. number : 16
    Structure
    E1EDPS5 : A&D: Price Scale (Quantity)
    Status: Optional , min. number : 1 , max. number : 99
    Structure
    E1EDP20 : IDoc schedule lines
    Status: Optional , min. number : 1 , max. number : 9999
    Structure
    E1EDPA1 : IDoc: Doc.item partner information
    Status: Optional , min. number : 1 , max. number : 8
    Structure
    E1EDPA3 : IDoc: Document Item Partner Information Additional Data
    Status: Optional , min. number : 1 , max. number : 99
    Structure
    E1EDP19 : IDoc: Document Item Object Identification
    Status: Optional , min. number : 1 , max. number : 5
    Structure
    E1EDPAD : A&D: Material Exchange
    Status: Optional , min. number : 1 , max. number : 1
    Structure
    E1TXTH1 : General Text Header
    Status: Optional , min. number : 1 , max. number : 1
    Structure
    E1TXTP1 : General Text Segment
    Status: Optional , min. number : 1 , max. number : 100
    Structure
    E1EDP17 : IDoc: Document item terms of delivery
    Status: Optional , min. number : 1 , max. number : 5
    Structure
    E1EDP18 : IDoc: Document Item Terms of Payment
    Status: Optional , min. number : 1 , max. number : 3
    Structure
    E1EDP35 : IDoc: Document Item Additional Data
    Status: Optional , min. number : 1 , max. number : 99999
    Structure
    E1EDPT1 : IDoc: Document Item Text Identification
    Status: Optional , min. number : 1 , max. number : 9999999999
    Structure
    E1EDPT2 : IDoc: Document Item Texts
    Status: Optional , min. number : 1 , max. number : 9999999999
    Structure
    E1EDC01 : SS: Service specifications general data
    Status: Optional , min. number : 1 , max. number : 9999999
    Structure
    E1EDC02 : SS item: Reference data
    Status: Optional , min. number : 1 , max. number : 10
    Structure
    E1EDC03 : SS item: Date segment
    Status: Optional , min. number : 1 , max. number : 10
    Structure
    E1EDC04 : SS item: Taxes
    Status: Optional , min. number : 1 , max. number : 10
    Structure
    E1EDC05 : SS item: Conditions
    Status: Optional , min. number : 1 , max. number : 16
    Structure
    E1EDC06 : Service line formula fields
    Status: Optional , min. number : 1 , max. number : 1
    Structure
    E1EDC07 : Service line user fields
    Status: Optional , min. number : 1 , max. number : 1
    Structure
    E1EDCA1 : SS items: Partner information
    Status: Optional , min. number : 1 , max. number : 8
    Structure
    E1EDC19 : SS items: Object identification
    Status: Optional , min. number : 1 , max. number : 5
    Structure
    E1EDC17 : SS items: Terms of delivery
    Status: Optional , min. number : 1 , max. number : 5
    Structure
    E1EDC18 : SS items: Terms of payment
    Status: Optional , min. number : 1 , max. number : 3
    Structure
    E1EDCT1 : SS items: Text identification
    Status: Optional , min. number : 1 , max. number : 9999999999
    Structure
    E1EDCT2 : SS items: Texts
    Status: Optional , min. number : 1 , max. number : 9999999999
    Structure
    E1CUCFG : CU: Configuration data
    Status: Optional , min. number : 1 , max. number : 99999
    Structure
    E1CUINS : CU: Instance data
    Status: Optional , min. number : 1 , max. number : 99999
    Structure
    E1CUPRT : CU: part-of data
    Status: Optional , min. number : 1 , max. number : 99999
    Structure
    E1CUVAL : CU: Characteristic valuation
    Status: Optional , min. number : 1 , max. number : 99999
    Structure
    E1CUBLB : CU: Configuration BLOB (SCE)
    Status: Optional , min. number : 1 , max. number : 999999
    Structure
    E1EDL37 : Handling unit header
    Status: Optional , min. number : 1 , max. number : 999999
    Structure
    E1EDL39 : Control Segment for Handling Units
    Status: Optional , min. number : 1 , max. number : 9
    Structure
    E1EDL38 : Handling Unit Header Descriptions
    Status: Optional , min. number : 1 , max. number : 1
    Structure
    E1EDL44 : IDoc: Handling Unit Item (Delivery)
    Status: Optional , min. number : 1 , max. number : 99999
    Structure
    E1EDS01 : IDoc: Summary segment general
    Status: Optional , min. number : 1 , max. number : 5

  • If you're having problems making an extension for Photoshop CS6 with Configurator 3..

    I was going to ask for help here, but before posting I decided to try one last experiment to see if it would work. Yesterday I tried making a simple one button panel inside Configurator and exporting it to Photoshop CS6. I put it in the plugins\panels directory. Start Photoshop, nothing... I tried looking at how to create an extension manually and signing it in order to install it with Extension Manager, and my brain nearly melted.
    So today I tried installing an older version of Photoshop (CS 5.5). The difference was that I selected Photoshop CS5/CS5.5 in the create new panel dialog in Configurator instead of CS6. Export Panel..It worked! Then I tried the same thing for my install of Photoshop CS6, selecting Photoshop CS5/CS5.5 as before in Configurator's dropdown menu.  Success!
    I hope this helps anyone who was stuck in the same place as me.

    Hmm, okay I just had a problem. I used an swf with a hue strip made in actionscript inside an swf loader in configurator. Tried exporting this to PS CS6's panels folder, and to my surprise it complete broke all of the other extensions in that folder. (ie. Photoshop refused to load any other non-defualt extenstions at all just because one was borked.). Very very stupid.  So I went back to PS CS5, everything was working perfectly. Then I closed it and went back to PS CS6, and suddenly my test panel was working again. I have no idea why PS CS5 "fixed" PS CS6, it doesn't make sense really.  I think I'll be going back to CS5 to do all my work as CS6 is really buggy about extensions, and I really need a color wheel for painting.

  • Problems with Macromedia Extension for Oracle Portal

    Hello,
    I’m learning about Oracle portal 10g(3.0.4). I'm having some problems about Oracle portal. Please help me as soon as possible.
    I created an Web Template using Dreamweaver MX 2004, and I´m tring to send this template to Oracle Portal through dreamweaver webservice (dreamweaver_webservice.zip) using Dreamweaver extension (dreamweaver_extension.zip) but when I try to connect using the extension to send my template I get Invalid Login message (I tried all possible passwords and logins for Oracle Portal and OracleAS). Please Help!
    Please help me or give me any materials about oracle portal. I want to study about this subject so if you have books in pdf format please send me.
    [email protected]
    thanks
    Douglas

    When I try to open the url with the ORMI port in the brownser I get this error message:
    Invalid protocol verification, illegal ORMI request or request performed with an incompatible version of this protocolvInvalid protocol verification, illegal ORMI request or request performed with an incompatible version of this protocol
    Ports I have tryed : 1852 and 3202
    ex:
    http://<host>:<port>/portalTemplate/portalTemplate

  • Problem LSMW + IDOC method for message type : MATMAS

    hi friends,
      I am using LSMW + IDOC method Message : MATMAS , idoc type : MATMAS03 .Setting every thing are fine. Finally Material is not created with error "message have been issued number : <idoc number>".
    data : material, industry type, material type, description, Basic unit of mesure.
    Please  help me.
    Balaji.T.

    Hi,
    I have nothing found regarding your issue. But maybe a look at SAP note 638058 will give you a hint.
    Regards,
    Klaus

  • User exit for idoc extension for material master (matmas05)

    Hello all,
    I have 10 custom fields added to anl idoc of basic type matmas05.
    i created a new segment under parent segment E1MARA1
    Now i want to find out the user exit where in i can write a code to read the data of this segment and populate into the data base table.
    Can anybody provide me with the name of the user exit?
    Regards,
    Roshani

    Check enhancement MGV00001 in SMOD.
    Exit Fm is EXIT_SAPLMV01_002
    Regards,
    Naimesh Patel

  • IDOC: Problem with data filter for IDOC extension field

    Hallo!
    I've created an idoc extension for the basic type DEBMAS06 that works fine. Now I want to use a data filter for one field ( company code ) of my segment. Every segment with a company code different from 100 should be filtered and not send to the other client. But what happend is that for all customers that have at least one company code different from 100, all segments including the one with cc 100 were deleted and a error "Segment ... does not exist for message type DEBMAS" appeared on the screen.
    Does anyone have any ideas about this problem?

    Not sure about changes to be made at the filtering options.
    An alternative would be sending the data to XI as it is and perform the mapping to remove the unnecessary segments.
    Disadvantage: Unnecessary processing of segment would be done at XI.
    Advantage: The integration logic would be completely handled by XI.
    Regards,
    Prateek

  • 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

  • Help Everyone: IDOC Extension Problem

    Hi All,
    Ive created an idoc extension for idoc type ORDERS01. I appended an extension ZE1EDK01 below header segment E1EDK01. Im trying to populate this through an exit but I cant seem to find the right values for these specifically the segnum and hlevel:
      wa_edidd-MANDT  = SY-MANDT.
      wa_edidd-SEGNUM = '000002'.
      wa_edidd-SEGNAM = 'ZE1EDK01'.
      wa_edidd-PSGNUM = '000000'.
      wa_edidd-HLEVEL = '02'.
      wa_edidd-DTINT2 = '1000'.
    How do I determine the values above?
    Also, I created an extension for item data segment E1EDP01. Im directly modifying the internal table of the IDOC and I want to populate the extension per line item in the idoc. How do I do this? Do I just append entries to EDIDD? How do I ensure that each entry appended corresponds to the correct line item?
    Please help. I really need to finish this in 2 hours.
    Thank you so much.
    Best Regards,
    Kenny

    Hi,
    I get what is the issue here. <b>It is not because of using CASE statement or IF condition in LOOP</b>.
    You are using user-exit EXIT_SAPLEINM_002. This user-exit triggers for each segment added to IDOC. So this is what is happening.
    - Segment E1EDK01 is added then user-exit triggers and it adds ZE1EDK01 segment.
    - Now the next segment is E1EDK14. After this segment also the exit trigges. When you loop at int_edidd the very first segment is E1EDK01 and it again adds ZE1EDK01 segment.
    So, for each segment in IDOC this exit triggers and add segment ZE1EDK01 under E1EDK01.
    <b>The solution is to use user-exit EXIT_SAPLEINM_011 instead.</b>
    This is very last user-exit which trigges in FM IDOC_OUTPUT_ORDERS and it has all the segment in it. So there is nothing wrong with your code but you are using wrong user-exit.
    Let me know if you have any question.
    Regards,
    RS
    Actually Srinivas is also right. If you use the user-exit EXIT_SAPLEINM_002 without using loop command and only using CASE statement it will work. <b>OR</b> you use user-exit EXIT_SAPLEINM_011. Its upto you.
    Message was edited by:
            RS

Maybe you are looking for

  • Applying A/P Credit memo

    2007A PL49 Have a GRPO in system.  Have not created an A/P invoice yet for the material.  Also have a vendor credit that has not been created in SAP either. How, if I can, apply the credit memo to the A/P invoice?  Do i create a service A/P invoice s

  • RFC connection error (VPN-access)

    Hi! I have the following error for the RFC connection: The RFC connection is setup as follows. /H/10.101.7.1/S/3299/H/10.151.6.194 10.101.7.1 = IP of our SAP Router 10.151.6.194 = IP of customer system The RFC connection is established: SAP Router (i

  • Computer can't recognize scanner

    how do i get my computer to recognize the scanner (Panasonic KB-S2046C) it's adobe acrobat 9.0 standard? I get the error message 162,0,0

  • Can you disable B channel snmp reporting on ISDN?

    Hello, We want to disable the snmp trap link status alerts for both B channels on a BRI interface, but continue to monitor the D channnel. Does anybody know if it can be done? Thanks!

  • Java...is it the best ?

    should i learn java? is it really that great...i know pascal and would like to expand my programming...im also interested in web design...