Old IDoc metada hanging

Hi
I have to remove one field from the extended IDoc , reimported the new IDoc to PI and deleted the old metadata and tried to create the new metadata in IDX2
my problem is the old metadata is always being created , even the Idoc structure does not have any more  the removed field, it seems that the old metada is hanging somewhere and and the new metada is not allowed to be created
plz suggest.

Hi Pavan
I did that
I deleted even the port and recreated it both from idx1 and idx2 , but as soon I execute the scenario then the Old metada data is created.
I checked  in SAP system and only the new structure of the IDoc exists.
I don not know where does the old metadata come from
Thanks.

Similar Messages

  • Old Problem of Hanging returned

    Back in March I couldn't get Premiere Pro to launch and it would always hang on the splash screen.  I haven't had to cut anything in 6 months but now I have a pressing job to do and I try to launch PP.  Initially it won't let me open my last saved timeline
    due to some codecs being missing.  It let me open a different old timeline, but the one I wanted was not opening no matter what I tried.  I shut down and tried to re-open and now it's back to the same old problem of hanging on the splash screen.
    Trying to find a way to contact actual Adobe support is impossible, so I'm back here to start the frustrating process all over again.

    Dear Users! this is a user-to-user forum. You can not contact Nokia support team via this forum and there are only few Nokia staff in these forums (Not the support team).
    Unfortunately, I don't know anything about your problem, it just seems to me your phone's keypad is worn off because of usage... but that might not be your case, please wait until you get a reply from another user or just take it to Nokia Care Point.
    Click on the Kudos Star, if you find my post helpful!

  • I have to change my e-mailadress in the appstore. No matter what I do, the old adress still hangs on. How do I change it?

    I have to change my e-mailadress in the appstore. No matter what I do, the old adress still hangs on. How do I change it?

    Settings>Store...tap the ID shown...sign out...sign back in with the ID you want to use.

  • Hey ,y phone is new just a 1month old its getting hang more then 15 times in a day

    hey ,y phone is new just a 1month old its getting hang more then 15 times in a day

    Try This...
    Close All Open Apps... Sign Out of your Account... Perform a Reset... Try again...
    Reset  ( No Data will be Lost )
    Press and hold the Sleep/Wake button and the Home button at the same time for at least ten seconds, until the Apple logo appears. Release the Buttons.
    http://support.apple.com/kb/ht1430
    If the issue persists...
    Connect to iTunes on the computer you usually Sync with and Restore
    http://support.apple.com/kb/HT1414
    Make sure you have the Latest Version of iTunes (v11) Installed on your computer
    iTunes free download from www.itunes.com/download

  • Old P3 CPU hangs when starting KMS with stock and ck kernels

    Hi, I have an old Pentium 3 machine on which I run Arch. If I try to boot the current stock kernel (or the ck kernel) the system freezes at boot. The system is still responsive, I can login via ssh but the screen is freezed. I nailed down the problem to KMS: booting with the nomodeset kernel option solves the problem. I have no problem in booting the lts kernel with KMS enabled, so I guess something changed between kernel 3.0 and 3.9 in this regard. Is anyone with old hardware experiencing this as well? It's not a big deal since I can live with lts kernel or disable KMS, but nevertheless I'd like to understand and possibly fix it. I can provide more informations on demand (right now I don't know what might be useful).
    Thanks

    snack,
             From experience, I have found that trying to use Arch Linux (a leading edge OS) on very old hardware is like trying to plug all the holes in an old wooden leaky boat when all you have is composite materials. It becomes increasingly difficult to keep older hardware working when using leading edge software.
    If you are happy to administrator the system using Arch then you may need to remain with linux-lts etc. The other problem I have run into is getting the older APG video cards to work & if you can get them working at a decent resolution getting them to render anything from a browser will bring the system to it's knees.
    My suggestion is trying a few Linux systems that are purpose built to be used on older systems. You may even have some luck with "enterprise" OSs such as Scientific Linux or Centos as they use older kernels & software.

  • AIF Automatic Reprocessing when using AIF as Monitoring Tool for ordinary Idocs

    Hi,
    we are using AIF in different ways as we introduced AIF after having a set of IDocs already set up in the traditional way. All new processes are set up in a way that AIF is responsible for the mapping and the following actions. But for the most older IDocs AIF is only used as a monitioring tool.
    We are also using the reprocessing facilities of the AIF working fine for the new designed processes. We set up also some reprossessing processes for the "old" IDocs and find out, that some of them are not working becausse of the "COMMIT WORK" within the function calls. So we get a dump saying that we are "POSTING_ILLEGAL_STATEMENT".
    Is there a way to solve the problem without redesigning the process (the SAP-Standard-FM L_IDOC_INPUT_WMMBXY is used in our special situation)?
    best regards
    Ignaz

    I have a similar thing happening here, but on my aging iMac8,1 (3.06, 6 gigs of ram, plenty of internal and external scratch space) No wacom here, a Logitech mouse though, running via USB overdrive.
    With me it's undos that are typically causing the hang, and as such, I notice it happening and don't keep clicking around. It hangs for anywhere from 30 seconds to 3 minutes or so and then I can continue working.  Once, it was happening on a document I had open for a while, once it was occurring on a file I opened, made an errant click, and hit undo.  This was a 46.6 MB CMYK tif. I also had it occur while drawing a simple selection with the polygonal lasso - each time it would hang on the third click.  That time, it would unhang, but then the selection would be all messed up and not display what was being selected.
    Each time it happens, I see photoshop pinned at 99-100% in iStat.  Doesn't seem to be related to running out of memory, as there is usually a good amount free when it's happening.  I tried using the internal drive as the swap, and that didn't seem to matter.
    I've been forced to go back to CS5 for the time being, but would love to see this solved.  Is there any further info I could provide?

  • We have to upgrade from SAP 4.0 version to ECC6.0(only EDI/IDOC effects)

    Hi All,
    We have to upgrde a system from SAP 4.0 version to ERP6.0, is there any difference in EDI and IDOC
    tables or their types in ERP6.0 from the 4.0 version, which we have to also consider or not.
    but if differences are there but SAP itself is taking care for that, then how the sap is taking care of that ..?
    Regards,
    Rohit Sharma
    Edited by: rohit sharma on Jun 19, 2008 1:26 PM

    I´m not sure what you mean by "old table to new table".
    The general table structure is not changed, VBAK + VBAP are still there. They may have been extended by additional fields, depending on how your system is implemented. It´s also possible, that if you activate any business function after the upgrade, that tables will get appends.
    The old IDOC structures working before the upgrade should work after the upgrade the same way since those structures are not touched.
    Markus

  • What is the serialization concept in ALE/IDOC?

    what is the serialization concept in ALE/IDOC?

    Hi Srinu ,
    IDoc Serialization means, sending/posting the idocs in sequence.
    We serialize IDocs in the following cases:
    · If you want the Integration Server to process the corresponding IDoc XML messages in the same sequence that it receives them from the IDoc adapter at the inbound channel.
    · If you want the receiver to receive the IDocs in the same sequence that the IDoc adapter sends them at the Integration Server outbound channel.
    The sequence at the Integration Server inbound or outbound channel can only be guaranteed if only IDocs are processed, and not if different protocols (for example, IDocs and proxies) are processed together.
    Do not confuse IDoc serialization using the IDoc adapter with the ALE serialization of IDocs.
    Prerequisites
    · The quality of service EOIO (Exactly Once In Order) must be specified in the message header.
    · The receiver system or the sender system must be based on SAP Web Application Server 6.40 or higher. If this is not the case, the quality of service is automatically changed to EO for compatibility reasons and the message is processed accordingly.
    Procedure
    If you want the Integration Server to process the IDoc XML messages created by the IDoc adapter in the same sequence that the IDocs are sent by your application, proceed as follows:
    · Enter a queue name in your application. You can use 16 alphanumeric characters. The prefix SAP_ALE_ is then added.
    The IDoc adapter checks the prefix and replaces it with the prefix of the corresponding Integration Server inbound queue (for example, XBQI0000).
    If you want the receiver to receive the IDocs in the same sequence that they are sent by the Integration Server using the IDoc adapter, proceed as follows:
    · In the communication channel, select the check box Queue processing for the receiver.
    The IDoc adapter replaces the prefix of the outbound queue (XBQO) with the prefix SAP_ALE_.
    You can display the individual messages in the qRFC monitor of the outbound queue. To do this, do one of the following:
    ¡ Use the queue ID in the list of displayed messages in the monitor for processed XML messages.
    ¡ Use the transaction ID in the list of displayed XML messages in the IDoc adapter.
    ¡ Call the transaction qRFC Monitor (Outbound Queue)(SMQ1).
    To navigate directly to the display of messages in the IDoc adapter, double click the transaction ID of a message in the outbound queue.
    To do this, you must have registered the display program IDX_SHOW_MESSAGE for the outbound queue in the qRFC administration (transaction SMQE) beforehand.
    In both cases, the function module IDOC_INBOUND_IN_QUEUE is called, which enables EOIO processing of the messages. The processing sequence is determined by the sequence of the function module calls.
    Unlike the other function modules (interface versions from the communication channel), with this function module you have to transfer segment types rather than segment names in the data records.
    Serialization of Messages
    Use
    Serialization plays an important role in distributing interdependent objects, especially when master data is being distributed.
    IDocs can be created, sent and posted in a specified order by distributing message types serially.
    Errors can then be avoided when processing inbound IDocs.
    Interdependent messages can be serially distributed in the following ways:
    Serialization by Object Type
    Serialization by Message Type
    Serialization at IDoc Level
    (not for IDocs from generated BAPI-ALE interfaces)
    Serialization at IDoc Level
    Use
    Delays in transferring IDocs may result in an IDoc containing data belonging to a specific object arriving at its destination before an "older" IDoc that contains different data belonging to the same object. Applications can use the ALE Serialization API to specify the order IDocs of the same message type are processed in and to prevent old IDocs from being posted if processing is repeated.
    SAP recommends that you regularly schedule program RBDSRCLR to clean up table BDSER (old time stamp).
    Prerequisites
    IDocs generated by BAPI interfaces cannot be serialized at IDoc level because the function module for inbound processing does not use the ALE Serialization API.
    Features
    ALE provides two function modules to serialize IDocs which the posting function module has to invoke:
    · IDOC_SERIALIZATION_CHECK
    checks the time stamps in the serialization field of the IDoc header.
    · IDOC_SERIAL_POST
    updates the serialization table.
    Check the following link:
    http://help.sap.com/saphelp_nw04s/helpdata/en/0b/2a66d6507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/78/2175a751ce11d189570000e829fbbd/frameset.htm
    Ex: ADRMAS, DEBMAS(customer)
    ADRMAS, CREMAS(Vendor)
    In this case, Before posting Customer Data or Vendor Data it requires Address Data.
    Rgds
    Sree m

  • Idoc related issues

    Hi
    We have designed an alv report that will display idoc details for FINSTA01 idoc.
    On clicking release button on the alv output.
    I have to work on the following requirement.
    "Map FINSTA01 to PEXR2001 to create idoc. Show the report with new idoc no and old idoc no"
    Is there any function module to map the above idocs? How we will do that. Please give me details.After mapping how can I generate a new PEXR2001 idoc programmatically.
    Regards,
    Sucheta.

    Hi
    I have used the following code for this functionality. Please suggest where I am wrong.
    CALL FUNCTION 'IDOC_READ_COMPLETELY'           "To read the segments of finst01 idoc
      EXPORTING
        DOCUMENT_NUMBER                = tb_output-idoc
    IMPORTING
       IDOC_CONTROL                   = wa_edidc
      NUMBER_OF_DATA_RECORDS         =
      NUMBER_OF_STATUS_RECORDS       =
    TABLES
      INT_EDIDS                      =
       INT_EDIDD                      = tb_edidd
    EXCEPTIONS
       DOCUMENT_NOT_EXIST             = 1
       DOCUMENT_NUMBER_INVALID        = 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.
         * Get data from the Idoc segments
    data: wa_edidd like line of tb_edidd.
    data: wa_Z1EXNA12 type Z1EXNA12, wa_Z1EXNA13 type Z1EXNA13, wa_Z1EXNA14 type Z1EXNA14,
          wa_Z1EXNA15 type Z1EXNA15, wa_Z1EXNA16 type Z1EXNA16, wa_E1IDKU1 type E1IDKU1,
          wa_E1EDK03 type E1EDK03, wa_E1EDK02 type E1EDK02,
          WA_E1IDT01 type E1IDT01 , wa_E1IDB02 type E1IDB02, wa_E1EDKA1 type E1EDKA1,
          wa_E1IDPU1 type E1IDPU1 , wa_E1IDKU7 type E1IDKU7.
          LOOP AT tb_edidd INTO wa_edidd.
            CASE wa_edidd-segnam.
              WHEN 'E1IDKU1'.
              wa_E1IDKU1 = wa_edidd-sdata.
              WHEN 'E1EDK03'.
              wa_E1EDK03 = wa_edidd-sdata.
              WHEN 'E1EDK02'.
              wa_E1EDK02 = wa_edidd-sdata.
              WHEN 'E1IDT01'.
              wa_E1IDT01 = wa_edidd-sdata.
              WHEN 'E1IDB02'.
              wa_E1IDB02 = wa_edidd-sdata.
              WHEN 'E1EDKA1'.
              wa_E1EDKA1 = wa_edidd-sdata.
              WHEN 'E1IDPU1'.
              wa_E1IDPU1 = wa_edidd-sdata.
              WHEN 'E1IDKU7'.
              wa_E1IDKU7 = wa_edidd-sdata.
              WHEN 'Z1EXNA12'.
              wa_Z1EXNA12 = wa_edidd-sdata.
              when 'Z1EXNA13'.
              wa_Z1EXNA13 = wa_edidd-sdata.
              when 'Z1EXNA14'.
              wa_Z1EXNA14 = wa_edidd-sdata.
              when 'Z1EXNA15'.
              wa_Z1EXNA15 = wa_edidd-sdata.
              when 'Z1EXNA16'.
              wa_Z1EXNA16 = wa_edidd-sdata.
            endcase.
            clear wa_edidd.
          endloop.
          data: tb_idoc_contrl type standard table of edidc with header line,
                tb_idoc_data type standard table of edidd with header line,
                tb_idoc_status type standard table of BDIDOCSTAT with header line,
                tb_ret_var type standard table of BDWFRETVAR with header line,
                tb_serial_info type standard table of BDI_SER with header line.
           clear wa_edidd.
          loop at tb_idoc_data.
           tb_idoc_data-DOCNUM = wa_edidc-docnum.
           tb_idoc_data-segnam = 'E1IDKU1'.
           wa_E1IDKU1-BGMTYP = 'PEX'.
           wa_E1IDKU1-BGMNAME = 'REMADV'.
           tb_idoc_data-sdata = wa_E1IDKU1.
           append tb_idoc_data.
           tb_idoc_data-DOCNUM = wa_edidc-docnum.
           tb_idoc_data-segnam = 'E1EDK03'.
           tb_idoc_data-sdata = wa_E1EDK03.
           append tb_idoc_data.
           tb_idoc_data-DOCNUM = wa_edidc-docnum.
           tb_idoc_data-segnam = 'E1EDK02'.
           tb_idoc_data-sdata = wa_E1EDK02.
           append tb_idoc_data.
         tb_idoc_data-DOCNUM = wa_edidc-docnum.
          tb_idoc_data-segnam = 'E1IDK02'.
          tb_idoc_data-E1IDK02 = wa_E1IDK02.
          append tb_idoc_data.
           tb_idoc_data-DOCNUM = wa_edidc-docnum.
           tb_idoc_data-segnam = 'E1IDT01'.
           tb_idoc_data-sdata = wa_E1IDT01.
           append tb_idoc_data.
            tb_idoc_data-DOCNUM = wa_edidc-docnum.
           tb_idoc_data-segnam = 'E1IDB02'.
           tb_idoc_data-sdata = wa_E1IDB02.
           append tb_idoc_data.
          tb_idoc_data-DOCNUM = wa_edidc-docnum.
           tb_idoc_data-segnam = 'E1EDKA1'.
           tb_idoc_data-sdata = wa_E1EDKA1.
           append tb_idoc_data.
            tb_idoc_data-DOCNUM = wa_edidc-docnum.
           tb_idoc_data-segnam = 'E1IDPU1'.
           wa_E1IDPU1-DOCNAME = 'PEX'.
           tb_idoc_data-sdata = wa_E1IDPU1.
           append tb_idoc_data.
          tb_idoc_data-DOCNUM = wa_edidc-docnum.
           tb_idoc_data-segnam = 'E1IDKU7'.
           tb_idoc_data-sdata = wa_E1IDKU7.
           append tb_idoc_data.
           tb_idoc_data-DOCNUM = wa_edidc-docnum.
           tb_idoc_data-segnam = 'Z1EXNA12'.
           tb_idoc_data-sdata = wa_Z1EXNA12.
           append tb_idoc_data.
           tb_idoc_data-DOCNUM = wa_edidc-docnum.
           tb_idoc_data-segnam = 'Z1EXNA13'.
            tb_idoc_data-sdata = wa_Z1EXNA13.
            append tb_idoc_data.
           tb_idoc_data-DOCNUM = wa_edidc-docnum.
           tb_idoc_data-segnam = 'Z1EXNA14'.
            tb_idoc_data-sdata = wa_Z1EXNA14.
            append tb_idoc_data.
           tb_idoc_data-DOCNUM = wa_edidc-docnum.
           tb_idoc_data-segnam = 'Z1EXNA15'.
            tb_idoc_data-sdata = wa_Z1EXNA15.
            append tb_idoc_data.
           tb_idoc_data-DOCNUM = wa_edidc-docnum.
           tb_idoc_data-segnam = 'Z1EXNA16'.
            tb_idoc_data-sdata = wa_Z1EXNA16.
           append tb_idoc_data.
          endloop.
          move wa_edidc to tb_idoc_contrl.
           wa_edidc-DOCTYP = 'PEXR2NA1'.
           wa_edidc-MESTYP = 'REMADV'.
           wa_edidc-IDOCTP = 'PEXR2002'.
           wa_edidc-cimtyp = 'PEXR2NA1'.
    DATA: W_DOCNUM TYPE EDIDC-DOCNUM.
           CALL FUNCTION 'IDOC_WRITE_AND_START_INBOUND'
             EXPORTING
               I_EDIDC                             = WA_EDIDC
             DO_COMMIT                           = 'X'
            IMPORTING
              DOCNUM                              = W_DOCNUM
             ERROR_BEFORE_CALL_APPLICATION       =
             TABLES
               I_EDIDD                             = TB_IDOC_DATA
           EXCEPTIONS
             IDOC_NOT_SAVED                      = 1
             OTHERS                              = 2
           IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
           ENDIF.
    data: tb_status type table of  BDIDOCSTAT with header line.
    append wa_edidc to tb_idoc_contrl.
    CALL FUNCTION 'IDOC_INPUT_REMADV'
      EXPORTING
        INPUT_METHOD                = 'A'
        MASS_PROCESSING             = ' '
    IMPORTING
      WORKFLOW_RESULT             =
      APPLICATION_VARIABLE        =
      IN_UPDATE_TASK              =
      CALL_TRANSACTION_DONE       =
      TABLES
        IDOC_CONTRL                 =  tb_idoc_contrl
        IDOC_DATA                   = TB_IDOC_DATA
        IDOC_STATUS                 = tb_idoc_status
        RETURN_VARIABLES            = tb_ret_var
        SERIALIZATION_INFO          = tb_serial_info
    EXCEPTIONS
      WRONG_FUNCTION_CALLED       = 1
      OTHERS                      = 2
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
         endif.
    The problem is tb_ret_var is returning nothing. When I am testing the newly generated idoc w_docnum of 'IDOC_WRITE_AND_START_INBOUND' fm in we19 it is generating a new idoc no. But the status of that idoc is 56. I am not getting the payment advice no.
    Please suggest what to do next
    regards
    Sucheta

  • Refresh Idoc Metadata in PI 7.31 Java Only

    Hello experts,
    We are facing issue to refresh the Idoc metadata every time when we change Idoc structure in ECC for Idoc outbound scenario.
    We have imported the latest Idoc structure in ESR and assigned that to MM,OM and IFolw. Still in message monitoring we can see the old Idoc structure.
    Is there anywhere else to import Idoc metadata like it used to be in Dual Stack idx2 ??
    Regards,
    Suman

    Hi Suman,
    If you are new with Idoc in PI  you try with the sap.help documentation: http://help.sap.com/saphelp_nw73ehp1/helpdata/en/50/980951964146f1a7f189b411796bae/content.htm
    Regards

  • IDOC_INBOUND_ASYNCHRONOUS FM not creating new IDOC?

    Hi,
    IDOC_INBOUND_ASYNCHRONOUS function module is not creating new IDOC in SAP.
    I configured all related functions against message type and idoc type.
    Please let me know the issue.
    I am processing old IDOC (created from non sap system) through BD87 and using custom function module. I called IDOC_INBOUND_ASYNCHRONOUS in custom function module.
    Chandra

    Hello,
    Aren't you getting any error messages ? You may check by creating watch points on the message id and / or number .
    Thanks

  • Problem with extension of idoc in XI

    Hello All,
    I've extended an Idoc in R/3 with new segment.
    That new idoc extension i've mentained in t/code IDX2
    Also, i've imported the new extended idoc in XI in IR.
    Next i've done the related mapoping for the new segment in IR.
    In ID, do i need to change the old idoc name with new extension idoc which i'm using in the Receiver Agreement
    After doing all these above modifications..i've receving the below mentioned error message
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>I::000</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: I::000</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Pls. let me know how i need to proceed further.
    Thanks in advance!!!
    Regards
    Prasad

    Hello Prasad,
    Go through these discussions....
    <IDOC_ADAPTER> ATTRIBUTE_IDOC_METADATA
    Re: ERROR: "IDOC_ADAPTER" / "ATTRIBUTE_IDOC_METADATA"
    File2IDoc Adapter Error
    Hope the above links are very helpful to you..
    Thanks,
    Satya Kumar

  • Large table for IDoc

    Hello Guru:
    Now the DB table EDID4 is very large ( more than 45 million records ) in our BW system, is there anyway to delete the content of the table but do not harm our BW logic?
    The system will read some data from the table when we try to read the monitor.
    Thank you.
    Best regards,
    Eric

    Hi,
    You can use SAP's archiving (txn SARA) to archive old IDOCs. These can alwasy be restored back into the system if required.
    You can select the IDOCs for archiving based on dates to delete IDOCs which are quite old and are not likely to be used.
    You can use an archiving job to automatically delete the idocs periodically (say idocs older than six months, the job running every week).
    cheers,
    Ajay

  • IDOC meta deta refresh related query

    Hi ,
    We are dealing with IDOC to file scenario.  The scenario is created and transported to Production .
    Suppose after that we have to add extra field in the IDOC .The ABAP guys  created the new IDOC in SAP system we deleted the old IDOC imported new one  in IR (dev) and done the mapping initally the field was not coming  but after  meta deta refresh (IDX2) the field has succesfully come in PI and sent to destination . We have transported the change ( IDOC and the message mapping ) to other env . Now do we have to refresh the meta deta manually in that environment also? or can we transport the meta deta also in other environment  to avoid manually deletion/updation of meta deta in evry env .
    Kindly update me
    Regards,
    Saurabh

    thanks again
    Even we were also have the same understanding that we don't need to do any thing extra for meta deta refresh in other env.
    but recently we are facing issue in pre prod that  the IDOC(in which extra field has been added ) get struck in ECC and does not come to PI untill we have not manually uploaded the meta deta .  so the client is asking that instead of manual deletion/updation of meta deta can we transport the meta deta or make the process automated .
    Regards,
    Saurabh

  • Testing of Idoc to file scenario

    Hi Gurus,
    I have completed the Idoc to file scenario, But how should I test the whole scenario??!!
    Because of my functional guy is absent for this week and I do want to test my scenario, whether its working properly or not??!!
    Note: As I knew, we19 tcode, it asks some Idoc number and other info to do the same.. could you please help me out?!!
    Thanks.,
    Stallin

    Hi
    Just for testing purpose..you can use WE19..
    First goto transaction WE02 and put Basic type : MATMAS03 as filter criteria, change your creation date to select little old idocs and run...on next screen your will see number of idocs "MATMAS03" with green status(if there is any in that period..otheriwse change period again).
    Then goto WE19 and put existing idoc number in the field existing idoc and and presss F8...On next screen press "Standard outbound processing".
    Can also use we19 and change control record ( Double click in EDIDC segment) to your sender / recever partner profile.. and run
    Thanks

Maybe you are looking for