Error while posting idoc in the receiving system.

i have processed idoc in the same system( sending and receiving idoc in the same system ) by creating a dummy logical sys and uploading a text file for customer details.The outbound processing is succesful and it shows a status message 3. But duriing the inbound processing it shows status as 51 with error as 'ENTER VALID VALUE'. but when testing using we19 it is posted sucessfully without any error..is there anything that i have to configure to process inbound idoc sucessfully?? can any suggest me the correct method for doing this.. suggestions please..
thanks
vidya sagar

Hi,
you need to make sure that in WE20 inbound processing parameters for you LS is maintained propperly. You need to give correct function module and enter whether IDoc should be processed immediately or IDocs should be collected and processed as batch. Also you may check whether the distribution model (BD64) is maintained correctly for the specific message type in the system for inbound processing.
Regards,
Kai

Similar Messages

  • Error while posting IDoc

    Hi,
    i am getting the following error while posting an IDoc: Program parameters for LS XXXXXXXX 2002 have not been set. Please suggest what can be the possible reason for it and the probable solution.

    First ,
    check the partner profiles in R3,
    i.e. a logical system is defined for XI , particluar Message type is added on inbond side and selected the releavnt messge type and and process code. this is all in WE20.
    defining a logical system is in SALE.
    then ditribute u r the model in BD 64
    once every thing is OK in R3
    on PI.
    create a RFC destination of type R3 which points to R3 , try remote log-on .
    this will be used in receiver chaneel
    and check u r receiver chaneel is defined under Business system of R3, and BS refers to same client where partner profiles are defined.
    and one of the following should be in place.
    check 'apply control record from payload' if ur explictly passing Control record from mapping
    otherwise,
    check sender service and receiver service in Receiver agreement and select appropriate systems.
    Regds,
    Suresh

  • SM 58 error while posting Idoc

    Hi
    I have installed a Netweaver XI  7.0 recently and have completed postinstallation tasks.
    Communication between all XI components (i.e IR, ID and SLD is working.)
    I am trying to test an Idoc to File scenario and while posting an Idoc from my R/3 system I am hitting upon this error "No service for system SAPD46, client 800 in Integration Directory".
    I have scanned SDN forums and came across note 940313 which talks about the registration  of R/3 system on SLD by one of the two methods as below..
    Business system
    Activities in the System Landscape Directory (SLD)(Create technical system):
          Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
          SLD (Business system):
          You can now explicitly assign a business system to this client.
          For more details, refer to the SLD documentation.
          Activities in system ABC (self-registration in the SLD):
          Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the "Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
          In system ABC, you can check your configuration with Transaction SLDCHECK.
          Activities in Integration Directory (import business system from SLD):
          You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
          Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
    I have performed activities highlighted in BOLD. But still error is same.
    My question from XI Gurus is that is there any way to know if the manual step of registering my R/3 system in SLD  is sufficient (As the SLD bridge for my R/3 system is not configured and I can not use auto registartion.)
    Is there any way to check if the R/3 system is successfully registered.
    Thanx
    Lovein
    Edited by: Lovein Khullar on Sep 17, 2008 11:16 AM

    Hi,
    I think it is due to basis problem, at ID one of service is not working.  Please check below mention link for configuration steps
    http://help.sap.com/bp_bpmv130/Documentation/Installation/Configuration_Guide_FP.pdf
    Meanwhile check all authorization for IDOC processing, else can't process idoc in XI
    For IDOC to FILE scenario follow below steps
    1. Define Logical system through BD54 after that assign logical system to client through SCC4 window in R3 & XI systems
    2. Define RFC destination through SM59 window in R3 & XI
    3. Define Port & partner profile through WE21, WE20 windows
    4. Trigger idoc from transaction code or test window through WE19.
    5. In XI configure SLD under define Product, Component, Technical & business system, it should be WEB as ABAP type.
    6. Import component from SLD to ID window meanwhile import idoc from R3
    7. Define target structure according to ur requirement and map accordingly
    8. Define ports IDX1 & IDX2 in XI
    9. In ID define scenario under import business system and configure steps according to ur requirement. Here IDOC is sender so no need communication channel and sender agreement.
    It will work without fail

  • SM 56 error while posting IDOC thru XI (File to IDOC) ????

    Hi ,
       When I am trying to post data into R/3 system thru MATMAS idoc,I have problem in posting data in R/3 system. In XI side the message is sent correctly to R/3 system, but in R/3 it is giving me SM 56 error, while mapping I tried to map only few fields, other mandatory fields I had populated with some constants and values and rest unwanted segments I disabled them. When I saw in error log it says PARTNER PROFILE is not properly set (but I checked Partner Profile is correct), when I checked the record it shows all fields (mapped with constants and values) except the mapped fields.
    Can anyone help me in this as I am struggling like anything...
    Thanks in advance
    Andy

    hi Andy,
    if you have a problem with control record have a look
    at my weblog:
    /people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

  • Error while posting Idoc for customer invoice.

    hi,
    I m posting Customer Invoice through LSMW using IDocs.
    Basic type is FIDCCP02 and message is FIDCC2.
    While posting the Idoc I m getting error as:
    'Document or line item does not exist for invoice reference'.
    I m not getting the error why it is asking for invoice reference because
    in FB01 it is not asking for any reference or anything.
    In Idoc all the item level values are coming prorperly.
    If anybody worked on such issues then please reply.
    -Thanx.
    -Umesh

    Hi Umesh,
    Try posting customer invoice through TCode - F-22. There it may be asking for reference number. Generally we post customer invoice by F-22 not from FB01.
    If you are getting error you can add reference field in your LSMW it may be mandatory in F-22.
    Ashven

  • Error while posting Vendor in R/3 System

    Hi ,
      When I am trying to post vendor data into R/3 system from flat file, I got an error in R3 System as
    "IDoc: 00000000000525200 Status: IDoc with errors added"
    "EDI : Partner profile not available"
    Please advice
    Thnx
    Andy

    Hi Andy,
    When you disable the EDI_DC40 field, the Idoc Adapter constructs the Control record based on the info from SLD.
    Please follow the below steps to make your scenario to work.
    In XI
    1)Define the Logical System for the Sender Business System in SLD.
    2)Make sure this infomation about LS shows up in the "Adapter Specific Identifiers" of the Business System in XI Configuration. If not, Clear the SLD Cache and try it again.
    In R/3
    1)Define the logical system in the R/3 using Tr.code BD54.
    2) Maintain the Partner Profile for this Logical system using TR.Code WE20 and define inbound parameters for the message type CREMAS.
    Try sending the message again.
    Hope this helps.
    Rgds,
    Sam Raju

  • Posting IDocs into the same system

    Hello Experts,
    We are having a requirement where-in we have to created a IDoc for the failed message in our RFC and hence it should be created in our own system and should be having status Error (Red).
    Is there any function module by which we can create the IDocs without specifying the receiver port. We tried debugging MASTER_IDOC_DISTRIBUTE FM at IDOC_CREATE_ON_DATABASE but it also expects the receiver information.
    Thanks in advance.
    regards
    rajeev

    No we haven't specified dummy partner. so we have to create a partner profile with the dummy receiver? And what port we should specify? Should it point to the same RFC destination?
    regards
    rajeev

  • Cash Management Error while posting GI for the reservation

    Hi,
    I am getting an error while trying to post the Goods Isuue for the reservation using MIGO transaction. The error is 'Level AR belongs to cash position (source symbol PSK)'.
    Please help me in solving this if anyone has any idea, let me know what am I supposed to do.
    Regards,
    Lavanya.

    go to VL02n, select the delivery#,enter & Change manually the Actual GI date to current date & press post goods issue(PGI).
    Hope this would resolve your problem.

  • Error while posting return delivery to backend system

    Hi All,
    We are facing problem when we are posting return delivery. Currently we are in ECS implementation. Our SRM is 7.0 EHP3.
    Scenario goes as, SC is created then PO is created then further confirmation is created and on creating return delivery of this confirmation, this return delivery goes error in process.
    Now on further analyzing, I found out that outbound IDoc in SRM is getting posted successfully but when ECC receives this IDoc it is saying please enter reason for movement 122. This reason for return is already entered while creating the return delivery. But this reason is not flowing in IDoc (Message Type MBGMCR and Basic Type MBGMCR01) in SRM and further to ECC. This field MOVE_REAS in IDoc is populating blank.
    Can anybody help me resolving this problem? Any pointers or SAP notes related to can also be suggested.
    Thanks
    Siddarth

    Hi Siddarth,
    Please implement the note below, which is included in SP05.
    2007628 - Return delivery cannot be posted in backend system as reason for return delivery is empty
    Regards,
    Wendy

  • Object (MARA) not found error while posting CLFMAS Idocs

    Good day,
    We are migrating the class hierarchy using Transaction CLHI (mesg. type - CLFMAS) from one SAP system to another.
    When we try to post CLFMAS Idocs in the receiving system, we are encountering this error-
    Object <  > from table MARA has not yet been created. For this reason, no class allocations can be maintained for this object.
    On further research, we found that this class (say parent class), has a subordinate class assigned to it that gets sent in the Idoc. The child class is not present in the receiving side, hence the error.
    Now when we try to ALE the child class first (before the parent), the same idoc as above scenario gets created with the same error that the child class is not present.
    These are our field values in the Idoc-
    Segment E1OCLFM  MSGFN   004
                                     OBTAB  MARA
                                     OBJEK   Child (or subordinate class) class
                                     KLART   001
                                     MAFID    K
                                     Object_table MARA
    Segment E1KSSKM  MSGFN   004
                                     CLASS   Parent class
                                     DATUV   00000000
                                     STATU    1
    There is one other issue that we are missing is that we are trying to migrate the material
    classes/ hierarchies. We are not yet mapping the material # to it. Why is it that the object table name is MARA.
    Please advise. TIA!!
    Liz

    Hi!
    Any ideas anyone?
    TIA, Liz

  • Missing document items in Sales Order in the receiving system

    Hello.
    We're doing passing of message type ORDERS (ORDERS05) from one system to another. Idocs were posted successfully but we can't find the document items in the receiving system if we view a particular sales order in VA03. Document items are present in the sending system.
    I checked segment E1EDP01 (document items segment) for the inbound idocs and found all items attached to the sales order but we can't see them in VA03 display.
    Appreciate help on how to proceed/check this issue.
    Thanks. =)

    If you have verified that the IDOC was complete in the receiving system, I would use WE19 to copy the IDOC in the receiving system (or copy to a development instance of that system) and run the process in debug....someone will have to watch the process, I think and see what is happening to the VBAP table during sales order build.

  • Error while posting material  in MB1c

    Hi
    how to open finace period in OB52 for period for 002/2009 as am getting error while posting in MB1c the error which am getting are period 002/2009 is not open for account type s and G/L 799999.
    Kindly help.
    Thanx.

    Hi Mukesh
    In OB52, you dont specify the GL account, you just open periods for the sub modules within FI.
    However, If you are getting an error while posting MB1c it must definitely be due to the MM periods not being opened
    Please go to MMRV - input your co code, and execute, it will tell you the current period which is open
    If your current period is not open, go to MMPV, input ur co code or codes, enter the new period and execute.
    This should solve your problem
    Rukshana

  • Please, 1. Please set the Receivables system options for this operating

    hi
    please i have this error:
    1. Please set the Receivables system options for this operating unit and ensure that the MO: Operating Unit profile option is correctly set with an operating unit that is set up in Receivables.
    can some one help me!
    thinks

    think you a lot mister.
    i am not the administrator of the base, our base administrator is not here for the moment, i have just the count apps and sqplus to change parameters.
    and the request :
    select fnd_profile.value('SO_ORGANIZATION_ID') from dual ;
    gives as result : 101!
    think you for all!.
    Message was edited by:
    brahim37

  • Error while posting the CREMAS03 Idoc

    Hi
    I a getting the Error while posting CREMAS03 idoc from File
    The ERROR: Status 65 ,Error in ALE Servics: Cross Company code does not exits..
    but when i cheked with the functional guys , the comany code exits..
    Any one have any idea
    SV

    Hey,
        seems you have given wrong enteries for logical system in sale or in WE20(patrner profile)
    Steps for ALE settings:-
    Steps for XI
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the R3 system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto IDX1.
         Create a new port.
         Give the port name.
         Give the client number for the R3 system.
         Select the created Rfc Destination.
    Step 3)
         Goto IDX2
         Create a new Meta data.
         Give the Idoc type.
         Select the created port.
    Steps for R3.
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the XI system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto WE21.
         Create a port under transactional RFC.(R3->XI)
         Designate the RFC destination created in prev step.
    Step 3)
         Goto SALE.
         Basic settings->Logical Systems->Define logical system.
         Create two logical systems(one for XI and the other for R3)
         Basic settings->Logical Systems->Assign logical system.
         Assign the R3 logical system to respective client.
    Step 4)
         Goto WE20.
         Partner type LS.
         Create two partner profile(one for XI the other for R3).
         Give the outbound or inbound message type based on the direction.
    Step 5)
         Goto WE19
         Give the basic type and execute.
         fill in the required fields.
         Goto IDOC->edit control records.
         Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
         Click outbound processing.
    Step 6)
         Go to SM58
         if there are any messages then there is some error in execution.
         Goto WE02.
         Check the status of the IDOC.
         Goto WE47.
         TO decode the status code.
    Step 7)
         Not mandatory.
         Goto BD64.
         Click on Create model view.
         Add message type.
    BD87 to check the status of IDOC.
    In case if not authorized then go to the target system and check in SU53, see for the missing object
    and assign it to the user.

  • Receiving Error : Please set the Receivables system options for this operating unit and ensure that the MO: Operating Unit profile option is correctly set with an operating unit that is set up in Receivables. while trying to create a new Customer.

    Hi All,
    We have set up a new Operating Unit in Oracle Apps. Now when I am trying to create a new Customer in that Operating Unit, I am receiving following error:
    ERROR MESSAGE:-Please set the Receivables system options for this operating unit and ensure that the MO: Operating Unit profile option is correctly set with an operating unit that is set up in Receivables.
    We do have MO: Operating Unit and MO: Default Operating Unit set properly at Responsibility level for the Responsibility through which I am accessing this form.
    Your help is appreciated!
    Thanks in advance,
    SKA

    You can refer this thread and check your MO operating unit is set or not https://community.oracle.com/message/3937028 thanks

Maybe you are looking for