ADRMAS idoc problem

We are uploading the data using LSMW
Step1: Customer General Data + Company code data
Step2: Customer Address Updation using ADRMAS idoc method in LSMW
But When I am doing it Its replacing the other fileds in the
Customer address which are not supplied in ADRMAS  idocs
Can anybody know how to tackle this problem ?
Useful answer will be rewarded.
Thanks & Regards'
Sreenivasa Reddy

Hi,
well there quite a lot of function to maintain address data.
For BAPI, I don't know.
The best is always to first read an address in order to get accurate data and structures and then maintain them.
To come back to your ADRMAS troubles.
The email segment (E1BPADSMTP) is not very easy to maintain.
e_mail field must be populated as well as EMAIL_SRCH (uppercase), CONSNUMBER, ...
From the idoc perpective, quite a lot of other fields are necessary
Segment E1ADRMAS: OBJ_TYPE=LFA1, OBJ_ID=yourvendor, CONTECXT=0001
Segment E1BPAD1VL: FROM_DATE, TO_DATE, probably COUNTRY, COUNTRY_ISO, LANGU_ISO, LANGU too.
Segment E1BPAD1VL1: ADDR_GROUP = BP
Maybe for your error, you tried to have E1ADRMAS-CHECK='X'
Hope this help
BR
Alain

Similar Messages

  • Update Problem in Inbound ADRMAS IDOC

    Hi Friends,
    Presently ADRMAS inbound IDOC creates a log for customer as follows:
    customer (vd03 or XD03)
    => Environment >> Account Changes >> All Fields  => All Changes .
    it has a lot of deletion. (even if nothing changes, my thought is it deletes everything and inserts it again)
    The question behind all this is: Can these logs be prevented? If every ADRMAS idoc generates this log , we'll get a very long log even when nothing or little has changed => we will not be able to see what went wrong with all these "fake" deletions.
    Please give some idea regarding this problem.
    regards

    Hi Suresh,
    The fields distribution,division and sales org  are to be passed in E1EDK14 segment with different qualifiers for each.
    Each Qualifier value represents a separate field.
    006     Division
    007     Distribution channel
    008     Sales organization
    segment name E1EDK14 006
    QUALF 006
    ORGID ZXXX  - ORGID holds the Sales division
    segment name  E1EDK14 007
    QUALF 006
    ORGID ZXXX  - ORGID holds the Distribution channel
    Hope this is clear now.
    Regards,
    Savitha

  • Problem with updating email fields thru  ADRMAS idoc

    Hi
    I have a ABAP program which calls the function module to create a vendor -ERP_IDOC_INPUT_CREDITOR'.
    During the creation of the vendor i can update the adress and telephone numbers but i cant input the email address .
    To solve this i am calling the function module (BAPI_IDOC_INPUT1-function module used in ADRMAS idoc).
    When i run the idoc it updates the field but when i call the Bapi in the abap program  it does not update the data that i have entered  in the function module .
    I tried doing a BAPI_TRANSACTION_COMMIT but it still does not update it.
    Any suggestions  to solve it.
    Also at the end of submitting the idoc it gives me a message
    BAPI SAVEREPLICA has been called successfully
    Is that what adrmas should be giving .
    Thanks

    Hi ,
    Check your BAPI Returen Parameters,  if it successfull then goto ADRC,ADR2,ADR6 tables and check your entry...
    email address in ADR6 table

  • ADRMAS IDoc Initial Load (ECC to C4C)

    Hi All,
    The Integration Guide for ECC to C4C integration using Netweaver PI downloaded for SMP explains how to set up the ADRMAS.ADRMAS03 IDoc to be triggered in ECC using Change pointers and flow to C4C via a Standard IFlow. The guide is self explanatory for setting up the BD64 Distribution Model, WE20 Partner Profile and even the Change pointers. It also talks about the pre-requisites, in this case the DEBMAS_CFS IDoc and how they should be maintained.
    Can anyone tell me how to do the Initial Loads for this IDoc? Are initial loads even required - I should think so since the Customer Addresses do need to be populated on C4C to begin with and can't just be populated in the case of Address changes in ECC.

    Hi Tim,
    We are following Chapter 8 for Initial loads, but there is no mention of how to ADRMAS IDoc's Initial load. There are details of the DEBMAS_CFS IDoc's Initial load which is a prerequisite for ADRMAS.
    When it comes to changes, the guide covers both DEBMAS_CFS IDoc's as well as ADRMAS. Do we not need to initial load for ADRMAS? If so, how would Customer Addresses move over from ECC to C4C initially?

  • Posting ADRMAS Idocs

    Hi,
    I am trying to post an ADRMAS idoc. This idoc contains address details for a particular suppler.
    Although this idoc posts correctly, I am finding that the vendor itself is not getting updated. Deeper investigations have revealed that the incorrect ADRNR is being picked up... The adrnr is not being lifted from LFA1 as I had expected, but from another table 'ADOWNERREF'.
    Can someone explain ...
    1) The rationale of why SAP is doing this and how the two ADRNRs are supposed to eventually coalesce
    2) Any particular settings in SALE that is causing this
    3) Any precautions one should use while posting the ADRMAS idocs
    Thanks and regards.
    Anand.

    Hello ,
    ADRNR is generated by the System automatically while creation Address.
    There is no place u can write ADRNR in the transaction.
    It varies system to system. It is Objectkey.If u are directly updating Vendor ,same
    ADRNR is Copied,but this Vendor when trying to access using transaction, it will
    go for dump.Bcoz the same Adrnr might be already in the System.
    Regards,
    Hazam

  • ADRMAS IDoc for customer address

    Hi,
    I am trying to send the customer address information via ALE. We are using a custom message type (ZDEBMAS) to send the customer data. I am aware that additional address information can be sent using ADRMAS. However, this message type is linked to a BAPI and I am unable to trigger the IDoc. I have activated the change pointers for ADR2MAS, ADR3MAS & ADRMAS as suggested in previous posts. I have also added the BAPI in the Model view with Object type  - BUS4001 and Method  -            SAVEREPLICA. Partner profiles have been generated as well.
    Can anyone guide me as to what I am missing? Any help is greatly appreciated.
    Thanks!
    Sheetal

    Hey,
    I think there are two possible problems:
    1. Please log in to XI system,
    check in transaction IDX1,
    which RFC destination is used for the system SAPR3D.
    than test this RFC destination in transaction SM59.
    2. Please check (via transaction WE30) that the IDOC in the ECC 6.0
    have the same fields as the IDOC in 4.6C.
    If they have different fields, than you must change the field "version" of channel of the 4.6c system (in the Integration builder configuration).

  • Mapping with IDoc problem

    Hi All
    I am having a problem where if I get over about 30 records from my 3rd Party in a file. This data is mapped to the Materials Master IDoc(MATMAS05) and it gets a mapping error when trying to run thru the mapping.
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_MM_MATCAT_MATMAS_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
    If I take this data from the Payload in SXMB_MONI and test in the Graphical Mapping tool in Integration Design it crashes with the above error. If I take this file and break into 2 parts and then send thru the mapping tool both files has no error. Does anyopne have any idea why this error occurs(could this be a memroy error - but for like 30 records) and how I can fix this as we would like to do a mass upload - about 9000 records(materials).
    Your help will be appreciated.
    Thanks
    Clinton

    Hi
    This is such a weird error.
    I have now started taking this file that I receive from the 3rd party with 200 records and tested it with the mapping tool. The results are as follow: From record 1-31 goes successful, 32-147 goes successfully and 148-200 goes successfully. So if I take the file as one file it crash, but if I break the file into the above 3 files it goes thru fine. for the first part it can only take 31 records, the 115, and then the rest. This does not make any sense, can someone please give me some advise.
    Thanks
    Clinton

  • G/L Idoc problem

    Hi All,
    I am posting an invoice from a flat file. First of all i will execute the program RSEINB00 and input the file name. This program will create an idoc from the flat file.
    Next, I will execute the program RBDAPP01 to process the idoc and post an invoice.
    The problem i am facing is, When there are more no of lines (G/L accounts) in the file ( Say 5948 lines ) the created IDoc data records are as follows.
    it has total 47872 segments. And it splits the idoc and each segment block is having 993 lines (G/L accounts).
    Segments 000001 007951 - 993 lines
    Segments 007952 015951 - 993 Lines
    Segments 015952 023951 - 993 Lines
    Segments 023952 031951 - 993 Lines
    Segments 031952 039951 - 993 Lines
    Segments 039952 047872 - 983 Lines.
    It will create a BDC session and whn i process the session error comes "No batch input data for screen SAPMF05A 0700" after 949th line. When i see th OSS note it says "Invoices with more than 949 G/L account line items must be split".
    My Question is Where can i do this setting inorder to restrict the G/L account lines to <949 in each segment block??
    Any insights will be appreciated.

    Hi Tushar,
    You can add your own codes in user exit to restrict the G/L account lines to < 949 during creation each segment block.
    Please search any user exits available in the function module which is used for inbound IDoc creation.
    In this case, your BDC will not give an error message because you already handled the max lines for G/L account during creation an IDoc for batch input process.
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

  • Inbound INVOIC01 IDOC problem

    Hi,
    I am working on inboind INVOIC01 idoc and i am facing some problem in that.
    When IDOC comes in it is creating application document ( Status 53 ). When i go and check in transaction MIR4 the application document (Invoice) is created. But the problem is, the Invoice is not being posted.
    When i see the invoice document, there is not tax code and so the invoice does not show any amount. I do not know why it is happening.
    Can anyone let me know what are the all required segments / fields for inbound invoice interface. What are the all configuration options required for it.
    Thanks,

    Hi Srinivas,
    Thanks for your reply.
    I have already configured the tax code config and now invoices are created correctly.
    But now i have one scenario which i am tying to figure out how to get it right.
    Let say for example
    <u>Example - 1</u>
    - i have PO with 1 line iteam with Quantity = 1 and amount $100. ( we mostly have PO with quantity =1 and only thing matter is $ value )
    - If the incoming invoice also have quantity = 1 and amount $100, it works fine.
    - But the problem is, sometime vendor sends the partial invoice. that is, quantity = 1 but amount $ 50. There can be multiple invoice with same quantity as PO line item different amount at different time. In this case i am gettng "Account Determination" error ( message  M8 147 ). Is there any way i can make this scenarion work. 80% of invoices comes like this. Please let me know
    <u>Example - 2</u>
    - i have PO with 1 line iteam with Quantity = 2 and amount $200.
    - If the incoming invoice also have quantity = 1 and amount $100, it works fine. Also, if it has quant = 2 and amount $ 200 it works fine. In other workds the quantity / amount ratio in invoice matches that of PO, it works fine.
    - But in few case we will get invoice with quantity = 1 ( PO as quant = 2) with amount 80 ( infact, any value other than 100. PO has $200, $100 / 1 each ) and in this case invoice is failing too.
    Can you please let me know, is there any setting in Logistic Invoice Verification, to support these scenarios.
    Thanks
    Pratik

  • Add segment to inbound idoc problem

    Hi ,
    I want to insert a segment in the middle of the segements inside a inbound idoc processing module.The problem is
    i am able to pass the segmnet name and data but i don't now what should be populated to the segment number (SEGNUM). Its value is coming as the same value of the previous segment when i checked in debugging mode.Can any body tell me how to populate the segnum field.
    Regards,
    Soumya.

    Have you tried by just keeping it blank.I will work fine if the hierarchy is kept correctly.

  • Strange IDoc problem in new System

    I am trying to post IDocs through a new production system that has just been set up. We have been running the scenario in the Test environment successfully for a few weeks.
    I send a batch of IDocs to the system, for example a bunch of four IDocs. Sometimes all four will process fine, other times one or more of the IDocs gop into error with the message
    There is no connection registered at the Messaging System for adapter type: File_http://sap.com/xi/XI/System
    If I select the messages in the monitor, I can sometimes get the message through, and sometimes it reverts back to this error, perhaps requiring a few attempts to process successfully. Sometimes the message just will not process.
    I am always resenfing four IDocs with the same data, so I really do not know what the problem could be.
    Any answers appreciated!
    BR,
    Tony.

    Hi,
    NEVER delete the files manually. As a admins we have to follow proper Uninstall and reinstall procedures as above one gentle man said.
    Here we will definately have some extra files also, like sapreorg, and backup file manually created if . Those also should be uninstalled properly.
    Also, we should maintain one back up copy of our file systems in each servers.
    just refer my system file structure, and proceed further.
    http://img158.imageshack.us/img158/591/bdfll0.jpg
    bye...

  • 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

  • Inbound - IDoc problem

    Hi Friends,
    Can anybody help me . I am facing a problem in IDOC inbound processing.
    My scenario in SALES PER RECEIPT - POS like this: I have to read XML (From PC) file and i have to post it.
    I am using Idoc - WPUBON01. After reading XML file i used Function module to distribute - MASTER_IDOC_DSTRIBUTE.
    In we02 i checked Idoc is generating but status showing 29.
    So run the report RSEOUT00. But i am getting message like 'No idoc is selected for processing'.
    Plz help me what i have to do. I created port also.
    Regards,
    P. Kumar.

    Hi,
    sarath has told valid point..don't use master_idoc_distribute,instead use the bapi
    bapi_idoc_input1..
    plz check the sample code how to do with inbound idoc,as u have got the data ,u just need to call the bapi and post it..
    check the code and proceed..
    FUNCTION zdtsint052f_gpoms_to_sap_gm.
    ""Local interface:
    *"  IMPORTING
    *"     VALUE(INPUT_METHOD) LIKE  BDWFAP_PAR-INPUTMETHD
    *"     VALUE(MASS_PROCESSING) LIKE  BDWFAP_PAR-MASS_PROC
    *"  EXPORTING
    *"     VALUE(WORKFLOW_RESULT) LIKE  BDWF_PARAM-RESULT
    *"     VALUE(APPLICATION_VARIABLE) LIKE  BDWF_PARAM-APPL_VAR
    *"     VALUE(IN_UPDATE_TASK) LIKE  BDWFAP_PAR-UPDATETASK
    *"     VALUE(CALL_TRANSACTION_DONE) LIKE  BDWFAP_PAR-CALLTRANS
    *"  TABLES
    *"      IDOC_CONTRL STRUCTURE  EDIDC
    *"      IDOC_DATA STRUCTURE  EDIDD
    *"      IDOC_STATUS STRUCTURE  BDIDOCSTAT
    *"      RETURN_VARIABLES STRUCTURE  BDWFRETVAR
    *"      SERIALIZATION_INFO STRUCTURE  BDI_SER
    *"  EXCEPTIONS
    *"      WRONG_FUNCTION_CALLED
    Purpose            :On recording the material consumption from       *
                        manufacturing tickets in GPOMS system, GPOMS     *
                        will report the data to the SAP system.Based     *
                        on this message, goods issue to the process order*
                        will be posted in SAP. This interface will       *
                        used for storage location managed materials      *
                        in SAP.                                          *
    Program Logic      :Loop at the data records of IDOC and to get the  *
                        Order number and SAP Movement type               *
                        If the Material document already exists for this *
                        Order number and Movement type then give error   *
                        else call standard FM 'BAPI_IDOC_INPUT1' to      *
                        Material Documents in SAP.                       *
    Declaration of Constants                                             *
      CONSTANTS :lc_item_create(25) TYPE c VALUE 'E1BP2017_GM_ITEM_CREATE',
                 lc_mbgmcr(6)       TYPE c VALUE 'MBGMCR'.
    Declaration of Variables                                             *
      DATA : lv_index TYPE sytabix,
             lv_retcode type sy-subrc.
    Declaration of Workareas                                             *
      DATA: lwa_e1bp2017_gm_item_create TYPE e1bp2017_gm_item_create,
            lwa_data         TYPE edidd, " Work area for IDOC
            lwa_control      TYPE edidc. " Work Area for control rec
    Read the control data information of idoc.
      loop at idoc_contrl INTO lwa_control Where mestyp = lc_mbgmcr.
    Extract the data from the segments.
        LOOP AT idoc_data INTO lwa_data
        WHERE docnum = lwa_control-docnum and
              segnam = lc_item_create.
    *->> Set the tabix of the internal table
          lv_index = sy-tabix.
    Move the Material Document Item Segment data
          MOVE lwa_data-sdata TO lwa_e1bp2017_gm_item_create.
    Modify the material document item data  internal table
          PERFORM sub_modify_idocdata changing lwa_e1bp2017_gm_item_create.
    *->> set the changed values to the IDOC SDATA
          MOVE  lwa_e1bp2017_gm_item_create TO lwa_data-sdata.
    *->> Modify the table
          MODIFY idoc_data FROM lwa_data index lv_index.
    Clear the Work areas
          CLEAR : lwa_data,
                  lwa_e1bp2017_gm_item_create.
        ENDLOOP.                                     "LOOP AT t_idoc_data
    Call the BAPI function module to create the
    appropriate Material Document
        CALL FUNCTION 'BAPI_IDOC_INPUT1'
          EXPORTING
            input_method          = input_method
            mass_processing       = mass_processing
          IMPORTING
            workflow_result       = workflow_result
            application_variable  = application_variable
            in_update_task        = in_update_task
            call_transaction_done = call_transaction_done
          TABLES
            idoc_contrl           = idoc_contrl
            idoc_data             = idoc_data
            idoc_status           = idoc_status
            return_variables      = return_variables
            serialization_info    = serialization_info
          EXCEPTIONS
            wrong_function_called = 1
            OTHERS                = 2.
        IF sy-subrc = 1.
          RAISE wrong_function_called.
        ENDIF.
      endloop.
    ENDFUNCTION.
    ***INCLUDE LZDTSINT052F_GPOMS_GMF01 .
    *&      Form  sub_modify_idocdata
    Modify the material document item data  internal table
    FORM sub_modify_idocdata
    CHANGING pwa_e1bp2017_gm_item_create TYPE e1bp2017_gm_item_create.
    contant declaration
      CONSTANTS: lc_261(3) TYPE c VALUE '261'.
      DATA : lv_aplzl LIKE resb-aplzl,
             lv_aufpl LIKE resb-aufpl,
             lv_subrc LIKE sy-subrc,
             lv_charg LIKE resb-charg,
             lv_uom LIKE pwa_e1bp2017_gm_item_create-entry_uom.
      CLEAR: pwa_e1bp2017_gm_item_create-reserv_no,
             pwa_e1bp2017_gm_item_create-res_item.
    *->> Get SAP storage bin & Storage type from the Z table
      SELECT lgtyp lgpla
        INTO (pwa_e1bp2017_gm_item_create-stge_type,
              pwa_e1bp2017_gm_item_create-stge_bin)
         UP TO 1 ROWS
        FROM zdtsint050_sttyp
         WHERE zstorage_typ = pwa_e1bp2017_gm_item_create-stge_type
          AND  zstorage_bin = pwa_e1bp2017_gm_item_create-stge_bin.
      ENDSELECT.
      IF sy-subrc NE 0.
        CLEAR: pwa_e1bp2017_gm_item_create-stge_type,
               pwa_e1bp2017_gm_item_create-stge_bin.
      ENDIF.
      PERFORM get_oper CHANGING pwa_e1bp2017_gm_item_create.
    Get the Reservation number and Reservation item number
    basing on the idoc data.
      SELECT rspos werks lgort
             INTO (pwa_e1bp2017_gm_item_create-res_item,
                  pwa_e1bp2017_gm_item_create-plant,
                     pwa_e1bp2017_gm_item_create-stge_loc)
             FROM resb
             UP TO 1 ROWS
             WHERE rsnum = pwa_e1bp2017_gm_item_create-reserv_no
             AND   matnr = pwa_e1bp2017_gm_item_create-material
             AND   charg = pwa_e1bp2017_gm_item_create-batch
             AND   aufnr = pwa_e1bp2017_gm_item_create-orderid
             AND   vornr = pwa_e1bp2017_gm_item_create-activity
             AND   bwart = lc_261.
      ENDSELECT.
      IF sy-subrc <> 0.
    Start of insertion for R31K993797
        CLEAR lv_charg.
        SELECT rspos werks lgort
             INTO (pwa_e1bp2017_gm_item_create-res_item,
                  pwa_e1bp2017_gm_item_create-plant,
                     pwa_e1bp2017_gm_item_create-stge_loc)
             FROM resb
             UP TO 1 ROWS
             WHERE rsnum = pwa_e1bp2017_gm_item_create-reserv_no
             AND   matnr = pwa_e1bp2017_gm_item_create-material
             AND   charg = lv_charg
             AND   aufnr = pwa_e1bp2017_gm_item_create-orderid
             AND   vornr = pwa_e1bp2017_gm_item_create-activity
             AND   ( splkz = 'X' or
                     splkz = space )
             AND   bwart = lc_261.
        ENDSELECT.
        IF sy-subrc <> 0.
    End of insertion for R31K993797
          SELECT SINGLE werks lgort
                INTO (pwa_e1bp2017_gm_item_create-plant,
                       pwa_e1bp2017_gm_item_create-stge_loc)
                FROM resb
                WHERE rsnum = pwa_e1bp2017_gm_item_create-reserv_no.
          CLEAR : pwa_e1bp2017_gm_item_create-reserv_no,
                  pwa_e1bp2017_gm_item_create-res_item.
        ENDIF.
      ENDIF.
    get SAP UOM
      SELECT SINGLE zsap_uom
                    INTO lv_uom
                    FROM zca_uom_conv
                    WHERE zext_uom = pwa_e1bp2017_gm_item_create-entry_uom.
      IF sy-subrc = 0.
        pwa_e1bp2017_gm_item_create-entry_uom = lv_uom.
      ENDIF.
    ENDFORM.                    " sub_modify_idocdata
    *&      Form  get_oper
         Get the operation
         <--P_PWA_E1BP2017_GM_ITEM_CREATE_RE  Segment
    FORM get_oper  CHANGING p_pwa_e1bp2017_gm_item_create TYPE
                   e1bp2017_gm_item_create.
      DATA : l_aufpl LIKE afko-aufpl,
             l_aplzl LIKE afvc-aplzl.
      REFRESH : i_op.
      UNPACK p_pwa_e1bp2017_gm_item_create-orderid TO
             p_pwa_e1bp2017_gm_item_create-orderid.
    Get the reservation and routing number for the order
      SELECT SINGLE
             rsnum
             aufpl
             FROM afko
             INTO (p_pwa_e1bp2017_gm_item_create-reserv_no,
                   l_aufpl)
             WHERE aufnr = p_pwa_e1bp2017_gm_item_create-orderid.
      IF sy-subrc = 0.
        CALL FUNCTION 'CONVERSION_EXIT_NUMCV_INPUT'
          EXPORTING
            input  = p_pwa_e1bp2017_gm_item_create-activity
          IMPORTING
            output = p_pwa_e1bp2017_gm_item_create-activity.
      ENDIF.
    ENDFORM.                    " get_oper
    i have modifeid the incoming data,in ur case its not needed ,only first few lines until the bapi u have to see..if u have any query let me know..
    Regards,
    Nagaraj

  • ALE: mapping IDoc fields to change document fields - TBD22 for ADRMAS iDoc

    Hi,
    I am currently try to find a table or way to extract the information of the TBD22 table (ALE: mapping IDoc fields to change document fields) for the iDocs/ Message Types:
    ADRMAS
    INTERNAL_ORDER
    PROJECT
    I am looking for a table that shows me to which SAP R/3 tables and fields the segments and fields of the above mentioned messages will be mapped to.
    When I add one of the above mentioned message types to the table TBD22 selection criteria I always receive the notification: "No table entries found for specific key".
    Could anybody determine Which table I have to use or why I cannot extract this information?
    Thanks in advance!
    Best regards

    Hi,
       Since we can not map the target IDOC when any of the field changes using nodefunctions , you can write UDF and check the same i.e if field1 changes or field2 changes or field3 changes then trigger new IDoc. This is one of the options that you can try...please try it once.
    Regards
    Priyanka

  • IDOC Problem From 46C To ECC6 For ORDERS05

    Hello
    I am trying to generate 46C version ORDERS05 basic type from ECC6 700 version.
    Within WE20(Partner Profiles) I have set the Seg. release in IDOC type to 46C to generate the old 46C segment. When I run my test again the IDOC that was generated is still version 700.
    Thanks for the help.
    Joe

    Gentlemen:
    The problem around this statement:
    ASSIGN (w_field) TO <fs_field>
    is explained as follows:
    1. In ABAP language, there are two ways for assigning a new value to a field-symbol.
    - Sentence: ASSIGN (values) TO <my_field_symbol>.
      In this case, the <my_field_symbol> receives from (w_field) the data type and value content of this variable. So, we keep that a FSymbol is assigned and, at the same time, receives an initial value.
    - Sentence: <my_field_symbol> = '/' or <my_field_symbol> = my_var.
      In this way, we only pass the content of the variable next to = sign. But before this, the field-symbol must had been assigned (using ASSIGN statement), in another case, the compiler raises an exception.
    Following the example of Federico... I think he tried to assign a field like this (please, supose the program imports the structure of a database table with a standard function, into a internal table which is looped by the work area w_field ):
    - If w_field contains 'BKPF-WERKS', so sentence ASSIGN will affect the field symbol, passing to this the data type and current content of table field BKPF-WERKS.
    - If w_field contains 'BKPF-.INCLUDE': *the column .INCLUDE obviously is not associated with a data type... so our statement ASSIGN... TO... never pass any data type or value to our field-symbol. So that, this field is never initialized properly, and when inmmediately you try to execute something like this: <my_field_symbol> = '/', the game (program) is over.. XD
    I hope this post was helpful for anyone...
    Best Regards!!
    RRG
    ABAPer(u) - EVOLution

Maybe you are looking for