Inbound IDOC messages Retention Period- Where to Check

Hi Gurus,
Where do we specify Inbound IDOC messages rention period.
In our system I do not see Inbound IDOC messages ( coming from ECC to PI) older than 15 days.
But I see Outbound IDOC messages ( PI to ECC) older than 15 days.Also I see non IDOC messages older than 15 days.
I checked in SXMB_ADM, Integration Engine Configuration and I do not see any parameter for IDOCS.
I appreciate any pointers.
Regards,
Ramesh.

Hi,
   As far as I know, there is no specific setting for IDOC mesages .
Retention period is generically set for all the messages in XI.
Inbound and outbound messages are always with respect to ECC and not PI.
(What you call inbound are actually outbound and vice versa).
Retention periods, can be viewed using SXMB_ADM transaction only.
Regards,
Ravi Kanth Talagana

Similar Messages

  • Validations and sutitutions while processing an inbound IDoc message

    Hi all.
    I have got the next question for gurus:
    FI sustitutions and validations are processed while creating a new FI documento via IDoc? I'm using the message type FIDCC2 I can't sustitute any field.
    Could you help me, please?
    Thank you in advance.

    Thank you for your answer, but we need to use the FI validations and substitutions because we want to perform the same checks and substitutions done while a FI document is created via FB01.
    Do you have any other idea?
    Regards.
    Edited by: Arévalo David on Feb 2, 2009 8:18 AM

  • How do we change the message retention period for XI ??

    HI Frnds,
    The current set up is to retain the message for 24 hours. Where do we need to change this?
    Regards,
    Raja Sekhar

    Check this guide:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/402fae48-0601-0010-3088-85c46a236f50
    Also check
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0068bc1-6f8c-2a10-52bb-c6ee3562feb2
    Regards,
    Ravi

  • Retention period not maintained

    Hi,
    When i'm doing data archiving for purchase orders,i got the message " Retention period is not maintained ".
    Please any one can tell where i have to maintain.

    Hai,
    In SPRO - IMG - MM - Purchasing - Define tolerance limit for archiving. In this maintain the residence time 1 & residence time 2 for the Purchasinh doc type & also with item category also.
    Define Tolerance Limit for Archiving
    In this step, you specify how long external purchasing documents are retained unchanged in the database before being archived.
    You can define two time periods, via which you control the archiving of the documents:
    Residence time 1 for items without a deletion indicator
    Before the deletion indicator is set for a document item, the system checks when the relevant item was last changed. In the process, a change in the PO quantity is taken into account in just the same way as a goods receipt, for example.
    The date of the last change is compared with the current date. If no change has been made within the residence time 1 entered , the deletion indicator is set for the item.
    Residence time 2 for items with a deletion indicator
    For document items for which the deletion indicator was set manually or during the archiving run, the system checks how many days have elapsed since the deletion indicator was set.
    The whole document is only archived if:
    The deletion indicator has been set for all items of the document
    None of the items have been changed during the residence time 2 entered - i.e. the last change is the setting of the deletion
    The archived documents are then deleted from the database.

  • Inbound IDOC for sales orders not posting the configuration data

    Hi all,
    I am facing a problem in posting the inbound IDOC (message type ORDERS). The configuration data maintained in the parent segment E1CUCFG and in the segment E1CUVAL is not getting posted though i am passing the data in these segments which is 100% correct.
    Can any one solve this problem

    Hi Ravi,
    Please check the two segments are active. You can do that in BD53.
    In BD53 enter message type, and make the segments active.
    If segments are active, it appears in white colour.
    After this post the IDoc and check with segments.
    If its useful, award points pls..
    Regards,
    Bharadwaj

  • Error Inbound IDOC for WP

    Hi,
    We are loading Inbound IDOC message type WPUBON and we got an error from transaction code WPER, it is saying : Generation successful, but you must call up the function again.
    IDOC was successfully generated and I attempted to re-process it and OK.
    Any idea where is the error located ?
    thanks !
    Chika

    Hi
    DESADV is the message type. Idocs are attched to the Message type
    you can search or list down the idoc types in Transaction WE30.
    If you want to the idoc types attached to message type DESADV you can find in WE57
    The idoc types attached to DESADV are
    DELVRY01 - Function module - IDOC_INPUT_DESADV1
    DELVRY02 -Function module - IDOC_INPUT_DESADV1
    DELVRY03 -  Function module - IDOC_INPUT_DESADV1
    Thanks & Regards
    Kishore
    Edited by: Kishore Kumar Chiluka on Apr 23, 2008 1:25 PM

  • Inbound Idoc Testing File Template

    Hello friends,
    Could any one guide me in preparing the Test file for testing Inbound IDOC (message type: ACC_DOCUMENT) and (basic type: Acc_Document01).
    Only these are the 4 segments I am going to use.
    E1BPACHE09
    E1BPACGL09
    E1BPACAR09
    E1BPACCR09
    Basically I would like to know how to create a template to upload multiple documents during testing and the procedure to upload.
    I am able to test post one document at a time thru WE19.
    Thanks for ur help.
    Sam.

    Hi Sam,
    Try this, to my knowledge this is only to test if idoc is posted properly or not (to check the configuration), we can only post one Idoc at a time i think...but try this...
    am not sure  but try this...
    Go to WE19-> acc_docume*>control on the data segment and copy it->insert(next to copy in menu bar) the segment at the same level> fill the data and post it ...to see..just try this...
    Thanks
    Ajay

  • Database error changing table ADR2 - Inbound IDOC Create Order

    Hi experts,
    I have a backgroud job for program RBDAPP01 to process inbound IDOC message type OILLDD. It woked perfectly for years. Few days ago, the job got short dump and cancelled. In Error log, it shows error MESSAGE_TYPE_X Database error changing table ADR2 in function module ADDR_SAVE_INTERN.
    I already try to activate trace log to see sql statement but still couldn't find anything suspicious. Have anyone been through this problem before? Please suggest.
    Regards,

    Hi,
         Please check if this SAP note is useful.  1300825
    Regards,
    Srini.

  • Urgent help required : Batch processing error of an inbound idoc

    hi,
       i have a problem while posting an idoc to the GL(FB01).
    i'm using an Inbound idoc message type : ACC_GL_POSTING
    idoc type : ACC_GL_POSTING01.
    Process code : BAPI.
    In the transaction code OBA7 i have enabled a particular document type as BATCH INPUT ONLY.
    i have set the option " Trigger by background program" in the partner profile (we20).
    while testing the process i'm getting the error "Document type -- is only defined for batch input".
    how can i overcome this error? can idocs be used to post for transaction that are batch enabled . plz help me.
    with regards.
    T.Jeyagopi.

    Jeyagopi,
    There are different types of Data loading into SAP.
    BATCH INPUT / BDC / IDOC / BAPI etc. BATCH INPUT are standard programs that take the data and update SAP. I don't think that is same as batch processing of IDOC.
    You might want to remove the setting of batch input, retain the batch processing in WE20 and try it out.
    In my opinion it should work.
    Regards,
    Ravi
    Note : Please reward points for the posts that help you.

  • 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.

  • 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 ordsp fm:IDOC_OUTPUT_ORDRSP

    my problem is  that idoc fails  when it comes in as a response of ORDCHG when user changes the delivery date in PO outbound idoc triggers with message type ORDCHG. Vendor sends the response as a confirmation of order via inbound idoc message type ORDRSP. it fails at that movement and gives an error ME 790(material number  differ from .............) it is comparing the value of segment E1EDP19 qualifier 001 field IDTNR with ekpo-matnr &ekpo-ematn.
    NOTE: there is value in segment and it is correct value. but when  inbound idoc fails it is taking blank value in fekpo and comparing with ekpo-matnr &ekpo-ematn and giving an error ME 790
    and when we reprocess the same failed idoc without any changes in it via WE19 it posted successfully
    one more thing i noticed in all failed idoc that segment E1EDK02 qualifier 002 not got populated which contains vendor acknowledgement number.
    but when we reprocess it in WE19 without doing any changes it posted sucessfully.
    thanks in advance.

    You say that "when we reprocess the same failed idoc without any changes in it via WE19 it posted successfully". What about if you reprocess the same iDoc via BD87 ? If you are using the same Function Module, this shouldn't happen, unless you have some very specific userexit code around the user or transaction type.
    Cheers, Paul.

  • AEDTM + UNAME not filled via HRMD_A inbound idoc

    Sorry if this is the wrong forum but I couldn't find any forum related to IDocs.
    I have an inbound idoc:
    message type: HRMD_A
    basic type: ZHRMD_A0701
    Processing the idoc is working, however, AEDTM and UNAME isn't filled (the fileds are empty). I would assume that those fields are filled automatically with sy-datum and sy-uname. I did some debugging and found the corresponding INSERT:
    IDOC_INPUT_HRMD
    - IDOC_PROCESS_HRMD
      - RH_IDOC_OBJECTS_SAVE
        - inbound_objects_block
          - RH_CREATE_INFTY_PA_PB
            - SAVE_PA_PB_INFTY
              - insert_pa_pb_objects
                INSERT (dbname) FROM <f_prel_db>.
    AEDTM and UNAME are emtpy in <f_prel_db>. Any idea why? Is this a known issue?

    HR inbound idocs actually do not override change date / time (aedtm, uname) with date/ user id of the user who processes the inbound idoc. These info should automatically be populated in the oubound idocs as is from sending SAP system.
    I guess the reason being is this is meant to replicate data (with all original info from sending system) to receiving system. If you notice in the receiving system, when HR inbound idocs are processed, change pointers are not recorded.
    Therefore, if the inbound idcocs are not senf from SAP, these info would need to be populated when outbound idocs are created. Otherwise, you may have to look at inbound user-exit to see if these fields can be populated in the idocs segments.

  • Inbound IDOC File Testing

    Hello friends,
    Could any one guide me in preparing the Test file for testing Inbound IDOC (message type: ACC_DOCUMENT) and (basic type: Acc_Document01).
    Only these are the 4 segments I am going to use.
    E1BPACHE09
    E1BPACGL09
    E1BPACAR09
    E1BPACCR09
    Basically I would like to know how to create a template to upload multiple documents during testing and the procedure to upload.
    I am able to test post one document at a time thru WE19.
    Thanks for ur help.
    Sam.

    Did you find the answer for you question?
    I am trying to do the same to run a LSMW that load data through FB50 but I don't find how to fill the structures.
    Thanks.

  • Error determining posting period(infostructure S008,Variant Z2,RC3) while creating Sales orders from Inbound IDOCS

    Hello,
    I am getting this Error message"error determining posting period(infostructure S008,Variant Z2,RC3)" while creating Sales order from Inbound Idocs in the IDOC,which is affecting sales order creation.
    While viewing this Info structure S008, I could see no records have been maintained. Wanted to know the reasons behind this Hard error?
    Is it something related to Date Field used in the Update Rules for this Infostructure which is causing this posting period error?
    Appreciate your inputs on this.
    Thanks and Regards
    Mohammed Roshan

    Thank you Jelena,I checked the Ship. Delivery dates in the IDOC which are for Current Fiscal Year- 20140703 and 20140711,Could there be any other reason for this error?
    Could it be an issue with e Update rule in this Infostructire S008
    Secondly when we try change the update rule thru MC25 for this Infostructure S008,It gives a message"
    "Maintenance of SAP standard updates not allowed"
    Kindly advice
    Thanks and Regards
    Mohammed Roshan

Maybe you are looking for