Inbound idoc  mess type:DESADV basic type: DELVRY03  Item text

Hi all,
W're having a inbound process to create inbound deliveries via IDOC.
mess type:DESADV basic type: DELVRY03 
We want to create a item text on the delivery via the IDOC.  Is this possible?
I see that there's a segment E1TXTH9 - E1TXTP9  to put in texts.
But as I see it, to create a text, we have to give the delivery nr in TDOBJECT TDOBNAME TDID  TDSPRAS LANGUA_ISO.
But since we are creating it, this is not possible.
Is there any way to create an item text on an inbound delivery via the IDOC?  And how.
Thanks a lot!
Caroline,

Hi Chris,
Before end of the ur functiond module (Idoc_input_xxxxxxx) create an Enhnacement spot  . at this point I hope so delivey will be created already .so now u can get the delivery number
**********The Logic for Text Field filling*******************
IF NOT  vbeln IS INITIAL.
DATA : L_FNAME TYPE THEAD-TDNAME,
       L_FID TYPE THEAD-TDID,
       IT_TLINE  TYPE TABLE OF TLINE,
       WA_TLINE LIKE LINE OF IT_TLINE.
CONSTANTS :C_FID TYPE THEAD-TDID VALUE '0004',
           C_FID1 TYPE THEAD-TDID VALUE '0007',
           c_Text(40) type c value 'xxxxxxxxx',
           C_LANG  TYPE THEAD-TDSPRAS value 'E',
           C_FOBJECT TYPE  THEAD-TDOBJECT VALUE 'BELEG',
           C_FFORMAT TYPE TLINE-TDFORMAT VALUE '*'.
Reading  the Idoc data table for Text field population
     READ TABLE IDOC_dATA INTO IS_EDIDD
                          WITH KEY SEGNAM =  c_segnam_e1edkt2.
     MOVE IS_EDIDD-SDATA TO IS_E1EDKT2.
     CONCATENATE mrm_RBKPV-BUKRS mrm_BELNR mrm_GJAHR  INTO L_FNAME.
     if sy-subrc = 0.
       MOVE: IS_E1EDKT2-TDLINE TO WA_TLINE-TDLINE,
             C_FFORMAT TO  WA_TLINE-TDFORMAT.
             APPEND WA_TLINE TO IT_TLINE.
          CALL FUNCTION 'CREATE_TEXT'
            EXPORTING
              fid               = c_FID
              flanguage         = C_LANG
              fname             = L_FNAME
              fobject           = C_FOBJECT
              SAVE_DIRECT       = C_X
             FFORMAT            = C_FFORMAT
            tables
              flines            = IT_TLINE
          EXCEPTIONS
            NO_INIT           = 1
            NO_SAVE           = 2
            OTHERS            = 3
          IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          ENDIF.
I hope it resolves ur problem.Please let me know if u have any
Queries.
Rgds
Sree m

Similar Messages

  • What is the message type and basic type used for catsdb in idoc help me

    what is the message type and basic type used for catsdb in idoc help me
    ANY IDOC FOR CATSDB PLEASE TELL,
    Regards,
    Jagrut BharatKumar Shukla
    points will be awarded

    Hi,
    Check these message types.
    ATT_ABS_WITH_COST and WORKSCHED_WITH_COST.

  • How to find IDOC Function Module for Basic Type:ORDERS05

    Hi,
    What is the Transaction Code to locate the Function Module linked to the IDOC Basic Type & IDOC Message Type?
    Appreciate Your Help.
    Thanks,
    Kannan.

    Hi Seshu,
    Thanks for your reply. While creating a Custom IDOC, How do I link the IDOC Function Module and Basic Type. Appreciate Your Help.
    Thanks,
    Kannan.

  • I want the message types and basic types for catsdb table

    i want the message types and basic types for catsdb table

    Hi Jagrut,
    Message Class is "LR".
    <b>Reward points, if helpful.</b>
    Regards,
    Atin

  • 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

  • Trigger workflow when IDOC Status 51  & with Basic Type "ORDERS003"

    Hi Experts,
    Can any one explaine how to create worlflow for "When Idoc status is 51 with the combination of Basic Type "ORDERS003" . If this condition will satisfy i need to send a mail using worklflow. For this one Bussiness type is BUS2102".
    Can you explaine any one please i am new to Workflow.
    Regards,
    Sri

    Hi,
    Please refer to the below thread. Hope it helps.
    Triggering workflow upon idoc fail
    Regards,
    Sridhar

  • IDOC communication between different basic type releases.

    Has anyone run into a scenario where a newer SAP release would like to send a message to a partner with an older SAP release, using a basic type that does not exist in the older system?  (eg. DELVRY05 which only exists in release 700)
    In this scenario, what is the best practice, other than to have the newer SAP system send an older basic type that does exist in the receiving partner?
    Thanks.

    Hi,
    You can do this by specifying the older release in the partner profile outbound settings (for message type).
    Under the "Outbound options" tab there is a field "Seg. release in IDoc type". There you can specify the older release and the IDoc will automatically be depricated when it is received in the receiving system.
    Regards,
    Gajendra.

  • INBOUND IDOC not updating the basic data field which is created newly

    Hi,
    i am creating an inbound IDOC for material master creation in that in basic data1 i have created 2 custom field in general data 1 is updating and another  is not updating with the value in iDOC.
    User exits codes are fine. but data is not updating.
    can some one help hw to resolve this..
    regards,
    thanigai

    Hi,
    Are you Debug the function module in  Process code of IDOC and use COMMIT WORK in that Function module.

  • How to Test, Inbound idoc ,with out the Sender System, using a Text File

    Hi Guru's .
    we wanted to test BLAORD03 inbound idoc (Message Type BLAORD).with out the SENDER SYSTEM.
    on the same client.
    we wanted to test this idoc with text file from our local machine.
    Can anyone give us detail steps.like how to create  File layout
    with Segment name,and values for the fields.how to pass this file to the system.
    Thanks in advance.

    Hi Aparna.
    My requirement is to test the idoc with Inbound File.
    Generate a file with the data entered through segments through we19 ,and use the same file for processing through we16.
    when i am trying to do this syst complaing about
    Partner Profile not available, and some times
    port not available. and some  times with
    'No further processing defined'.
    but i maintained part profiles and port perfectly.
    Can you help me in testing with test 'File' port.

  • IDoc User exit: OREDRS (Basic Type ORDERS05)

    hi experts,
    I need to enhance FM u201CIDOC_INPUT_ORDERSu201D. So I had created the new project ZENHVEDA via tcode CMOD and under this new project, I assigned the VEDA0001 enhancement. I wanted to enhance Function exit EXIT_SAPLVEDA_001 (INCLUDE ZXVEDU03). But I had encountered this message:
    Program names ZX... are reserved for includes of exit function groups. Message no. DS027
    Any ideas what is this about? Appreciate so much.
    TQ.

    TQ very much.. I'm able to create now..
    Have a great day ahead...
    TQ. TQ

  • Vendor Address in IMessage type ORDERS basic type ORDERS01

    The idoc has three such segments E1EDKA1 AG: E1EDKA1 LF : E1EDKA1: WE. The segment   E1EDKA1 LF  shows the partner number but does not bring in the vendor address. What are we missing..please guide?
    Thanks

    Check if the address fields have been mapped
    1) Go to transaction WE30.
    2) Give the object name as ORDERS01
    3) Click on Display(F7)
    4) It will display the list of segments used for the IDoc
    5) Click on any segment and click on Segment Editor (F5)
    6) It will display the field names
    reward points if it helps
    regards
    Biju

  • Inbound IDoc incurs FI/CO interface error: Line item entered several times

    We encountered an error in an attempt to post a financial transaction document with multiple line items. The Paid In/Paid Out IDoc 210266 was created in the transaction WPUF as follows:
    Customer: 711
    Transaction Date: 08/22/2008
    Transaction Type: ZPOU   (Paid out)
    Item __ Acc.assgnt obj. ____ Cost Ctr __ Amount __ Crcy
    1________________________7110150____100______USD
    2________________________7110150____100______USD
    1________________________7110150____200______USD
    2________________________7110150____200______USD
    The IDoc status was 64 (ready to be transferred to application).
    Next we ran the interface program RWPOS_PARA_ENQUEUE and saw the message that the IDoc was fully posted. However, when we checked it in WE02, we saw the IDoc had actually failed. In WPER, we saw the error message:
    u201CFI/CO Interface: Line items created several times.u201D
    We double clicked on the error message to bring up the following diagnosis:
    FI/CO interface: Line item entered several times
    Message no. RW014
    Diagnosis
    The following document information was transferred several times:
    *Reference document "U0000001M8"
    *Reference organization ""
    *Item number "0000000001" .
    System Response
    The document information keys must be clear.
    Procedure
    This is a system error of the application which was called up.
    I drilled down to the SAP code trying to find what condition triggered this error message. The only place where this message is called is in the include program LRWCLF01, inside the subroutine CHECK_ITEMS. It seems that the system doesn't like the repetition of the item numbers in the IDoc. We consulted a functional consultant to see if we should change the second pair of items 1 and 2 in WPUF to 3 and 4. His answer was no.
    We would like to get the expert advice from this forum to help us solve this problem. Your time and effort will be appreciated.
    Thanks,
    Ning
    Edited by: Ning Hu on Aug 22, 2008 2:45 PM
    Edited by: Ning Hu on Aug 22, 2008 2:50 PM

    Just a guess, instead of
    Item __ Acc.assgnt obj. ____ Cost Ctr __ Amount __ Crcy
    1________________________7110150____100______USD
    2________________________7110150____100______USD
    1________________________7110150____200______USD
    2________________________7110150____200______USD
    try:
    Item __ Acc.assgnt obj. ____ Cost Ctr __ Amount __ Crcy
    1________________________7110150____100______USD
    2________________________7110150____100______USD
    3________________________7110150____200______USD
    4________________________7110150____200______USD
    Rob

  • Essential Transfer Parameters Missing in record during Inbound IDOC process

    Dear Gurus
    We are creating a Inbound delivery in one system, we have made all the custom settings for IDOC processing for inbound and outbound idoc in both the systems. Upon the execution of inbound delivery, the system 
    During the Inound delivery processing, the outbound IDOC is successfully distributed. However in the receving system, the IDOC is not posted and it throws the below erroe\r
    Essential transfer parameters are missing in record: 0180000055 000010 / Mess number 561 and message type E
    We are using Outbound IDOC mess type DESADV basic type DELVRY01 process code DELV with FM IDOC_OUT PUT_DELVRY
    In the receiving system message type DESADV , process code DELS, and FM IDOC_INPUT_DESADV1
    What is that which is going wrong.
    Please help me out
    Thanks

    Hello
    To create inbound delivery from outbound delivery, use following setting -
    Outbound idoc -
    idoc type - DESADV01
    message type - DESADV
    Process code - SD05
    FM - IDOC_OUTPUT_DESADV01
    Inbound iDOC -
    Message Type - DESADV
    Process Code - DESA
    FM - IDOC_INPUT_DESADV
    Idoc Type - DESADV01

  • Inbound Idoc with T-code: BORGR ( Inbound delivery create) EDI cannection

    Dear all,
    Kindly help me to create inbound delivery with BORGR transaction.
    Here the we have to create the inbound delivery in the system with the help of vendor number and material without using Scheduling agreement number in BORGR
    Please suggest the processing code and the function module required for the BORGR document posting.
    I have done the following steps u2026but not able to post the dummy idoc through WE19 .
    1.     Use standard message Type DESADV (T code: WE81).
    2.     Use standard IDOC type DELVRY05 (T code: WE30).
    3.     Assign message type  to IDOC Type ( Tcode: WE82).Message Type:-DESADV, Basic Type:-DELVRY05,Release 700
    4.     Use standard assignment of process code DELS with the message type DESADV ( Tcode: WE42)
    5.     Inbound Function Module :  IDOC_INPUT_DESADV1 ( T code : WE57)
    6.     Define Port type File (Tcode: WE21) Port u2013 EDI_ASN Inbound Delivery.
    7.      Define Partner Profile (Tcode: WE20) Inbound Parameters.
    8.     Enhancement can be done in inbound IDOC as per the business requirement. Business has confirmed Field name wise Inbound IDOC data which will be received from vendor and all fields are available in the standard IDOC type DELVRY05.
    Please help if anything more required for posting dummy idoc .
    Thanks and regards,
    koshti

    Hi Dick,
    just one additional hint as we had recently such problems :
    It my happen that DESADV creates an inb.del <b>w/o</b> packing the HUs (idoc status is 'yellow' instead of 'red'). To avoid this OSS #912470 is the solution.
    Kind Regards
    Kay

  • Inbound/Outbound Delivery using DESADV01 Inbound IDOC

    We are trying to use Message type DESADV, basic type DESADV01 to represent inbound and outbound material deliveries. Our SAP system is configured to accept these IDOCs and apply process code DESA which calls function module IDOC_INPUT_DESADV.
    Our question is which of DESADV01's Segment-Field is used to tell the FM that we are talking about an Inbound or an Outbound delivery?
    I have read something related to E1EDL21-LFART, but this field seems only present in basic type DELVRY01. Is there something similar in DESADV01?
    Cheers

    Thanks for your answer Anji.
    We are not having problems with the direction of the IDOC. The IDOC is always Inbound to the SAP system, as we want it to be. However the delivery which the IDOC represents can be an inbound delivery (material has entered a certain plant) or an outbound delivery (material has come out of a certain plant).

Maybe you are looking for