IDOC in  Ibound  processing problem...

Hi All
  i have  to transfer data from one server to other and i used Idoc. with ale.
All works fine in Outbound process with status 03.
but in Inbound  processing the status is 51.(Documant not posted .).
and i am not able to se the data in the inbound system.
up to point  must be awarded..
Regards..
lakhan......

Hi lakhan,
Have u created function mdoule & process code for ur idoc
Pleasae go throught this
Create Idoc type – Transaction WE30.
Idoc type     Idoc segments
Z_idoc                                    
Create Message Type – Transaction WE81.
Message type
z_mess
Assign Message Type to Idoc type – Transaction WE82.
Idoc type                    Message type
z_idoc            z_mess
Create a function module through SE37
z_idoc_input
Assign characteristic of function module   BD51
Assign fn module to Idoc type and Message Type WE57
Idoc type     Message type      Fn Module
z_idoc     z_messs         z_idoc_input
Create Inbound process code and assign inbound function module – Transaction WE42.
Process code     Inbound function module
zcode                       z_idoc_input
Create a distribution Model - Transaction BD64
Create distribution model for distribution
with the message type of z_mess
Update inbound parameters of the Partner profile – Transaction WE20
For the Logical system A for the above message type update the partner profile
inbound parameter and specify the process code of Zcode.
<b>Regards,
Azhar</b>

Similar Messages

  • IDoc-XI-File Processing problem

    Hi There -
    I am looking for expert help in resolving following issue:
    We developed multiple IDoc-XI-single File using BPM (with time=1 min) in SP14. The scenario was working fine.
    Now we transported to XI SP15 on UNIX. While testing some messages are in recorded status with Q stopped error. But File is being created with some messages.
    Help in resolving this issue is appreciated.
    Regards,
    Tom

    Hi,
    If there some idocs are missing while collecting, then try to do Local Correlation instead of Global Correlation.
    Suugested SAP Notes- 852019
    Just look into this-
    /people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages
    Message scheduled (waiting )
    /people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
    Hope this helps,
    Pls acknowledge
    Regards,
    Moorthy

  • Problems with processing outbound IDocs in background processes

    Hello everybody,
    I have a question for working with ABAP-PSS Ports.
    The behvaiour is that I want to send master data, for example customers, to a function module. This function module works like an converter which process and writes the files in the filesystem.
    Following situation:
    - I have defined a partner System with different message types, for example DEBMAS and everthing what is necessary to replicate data to partner systems.
    - I have defined also a Port like ABAP-PPS Port for calling my own function module.
    - If I runs the program I process only 50 Idocs per process because otherwise i can happen that there are to many look entries in the system and the job crashs. (For example all customers are around 50000 Idocs).
    Now my problem is that the worker for processing idocs starts each process in the foreground and in parallel.
    But this is very strange! Because then all dialog processes are reserved and the system will be very slow!
    How can I configure the Port or what have I to implement in my fucntion module to start processing in background (this is the very important point) and maybe allow the program only to use one or two process at the same time?
    I have found on the function module EDI_DOCUMENT_CLOSE_PROCESS which I the parameter "Background". What thas this mean? I have set B for this but it has no effect!
    Regards
    Christian

    I know that for inbound interface it is possible to define if in foreground or background and if parallel processing is allowed.
    Who knows how I can do this also for outbond?

  • IDOC is not processing in R/3 with status 64(Urgent)--Production issue.

    Dear Folks,
    Here we are implementing MIRROR sytem for data extraction in to BIW.
    I had gone through the steps in PDF file(How to minimize down thime for Delta Initialization) which has given by SAP.
    These are following steps I had performed in BW production
    1. Using RSADMIN transcation- Assigned one user as a Debugging user.
    2. With the Debugging user Created one infopackage on Purhcasing ITM datasource--
        In data selection tab, I given date as from 2002 to 2003
        In Update tab, I selected update mode as Initialize Delta process-               without data transfer and Uncheck Update Data in master   system immediately
       In schedule tab I selected option Start Data load immediately then Start extraction.
    3.Data was requested and It was intialized properly with green status 1 from 1 Records.
    4. In details tab Request, Extraction, transfer(IDOC and TRFC), Processing everything in Green color.
    5.As per document I have checked in R/3 for IDOC with status 64 using transaction BD87/WE05
    Problem is that IDOC is not processing in R/3 system. for that IDOC I have checked in BW montior screen using the option <b>IDOC list in Source sytem</b>, here also it is not showing any IDOCs.
    Please let me know why BW sytem is not sending any IDOCs to source sytem.Is there any settings I could have miss in BW aswell as in R/3 system.
    Note: In BW production I successfully loaded master data from R/3. aswell as I triggered infopackage-Initialization with data transfer, it is showing IDOC number properly in R/3 system.
    Points is Assured for all replies.

    Hi,
    - check you RFC destination (normal test + authorization test)
    - Check you partner profiles in WE20 and its ports WE21
    - from the source system tree (RSA13) right click your source system and perform a check
    - the best is to restore your source R/3 source system from BW (right click on it ans select RESTORE); you'll need to be able to log in the source system as an admin as well as opening the source system for customizing in SCC4 so that BW can recreate the correct partner parameters automatically; the best is to do that with your basis group.
    hope this helps,
    Olivier.

  • Inbound IDocs will only process immediately

    Hello.  I have been having an issue with our inbound INVOIC02 IDocs coming from our EDI server.  We are processing a high number of invoices and I wanted to change the processing from immediate to collective.  The immediate processing is causing a strain on our EDI server.  I would like the IDocs to come into the SAP system, but stay in a status 64 until a background job runs to process them.  I changed the partner profile for the vendor from Trigger immediately to Trigger by background program.  For some reason, the IDocs are still processing immediately. 
    Here are some of my settings:
    EDI side Function Module:  IDOC_INBOUND_ASYNCHRONOUS
    SAP side Function Module: IDOC_INPUT_INVOIC_MRM
    Partner profile setup:
    Partner no: (vendor #)
    Partn. type: LI (vendor)
    Message type: INVOIC
    Process code:  INVL
    Processing by function module: Trigger by background program.
    Please let me know if you have any recommendations as to how I can get these IDocs to process from a background program instead of immediately.  Am I missing another setting for this?
    Thanks,
    Lisa

    Hi Klaus,
    form the mentioned options, I would give enqueue / dequeue a second try.
    I would use customer (/sender) as key field for your locking object.
    If you try to set the lock right in the beginning of your FM, whole customer should be locked for processing. Second test is of course, if already a sales order exists.
    Maybe here the problem occurs: when you have some parts in update task, select for sales order is not successful for some (micro-)seconds.
    Solution for this part: use synchronic booking / commit work and wait. Maybe make a test with a select for VBAK in the end of your FM to test existence -> if not successfull, you know you identified your problem.
    If this is your problem, you should make a new enqueue after commit (because it will be deleted by commit) and wait until DB gives you new VBAK entry.
    I would start with a test, why all this different locking options don't work (instead of looking for a different locking option): make a select after your sales order creation. If this is not successfull, then here is your starting point.
    Regards,
    Christian

  • REG: Error in IDoc adapter outbound processing

    Hi All,
          I had a couple of doubts regarding these IDoc's.
    1)        I am dealing with the web services to IDoc Scenario. When i am activated my wed services it               is giving an error like
    "IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP" and "Only asynchronous processing supported for IDoc adapter outbound processing"
    Can any one help me to Solve my Problem
    2) How to find out whether the IDoc is of synchronous or Asynchronous mode
        and how to  handle the synchronous type of IDoc's
    Thanks in advance.
    with Regards,
    Kalyan Dannapaneni.

    Hi Kalyan,
    IDOCs are only Aynchronous (EO or EOIO).
    If you want to call Synchronious, you will have to find remote enabled function modules (RFCs, BAPIs).
    Or you have to use the ccBPM Synch-Async pattern to have an synchronos call passed to an IDoc, waiting for the Acknowledgement. In your situation I would check if a similar BAPI/RFC exists on your Backend SAP system.
    Best regards,
    Silvia

  • IDOC: Incorrect function module problem

    Hi,
    I am working on inbound IDOC processing. I created an extension for an IDOC. I created custom segment & included it in the extension that I created. The Message type was also custom. (I merely copied an existing standard Message Type for some other purpose). I also assigned Function Module to Message Type & IDOC type. I have other necessary settings configured as required. The problem that I am encountering is as follows:
    Incorrect function module IDOC_INPUT_SHPCPR called up
    Message no. B1044
    Diagnosis
    The function module IDOC_INPUT_SHPCPR, which was called for the application input, was not able to process the IDoc. A possible cause is that the IDoc has wrong message type or IDoc type.
    Procedure
    Please check the message type assignment for the application function module in the ALE customizing.
    Now to troubleshoot the above error, I made sure that I have an entry with FM. IDOC_INPUT_SHPCPR,  IDOC Basic Type ,custom  IDOC extension & custom Message Type. But even then I see the above error. This error appears as Status 51 for the test IDOC that I processed.
    Can anyone please tell me how to solve this? Thanks in advance.

    On line 49 of the function module :
    * Loop through the IDocs' control records
      LOOP AT idoc_contrl.
    *   Check the IDOCs message type
        current_mestyp = idoc_contrl-mestyp.
        PERFORM idoc_message_type_check
                     TABLES   idoc_status
                     USING    idoc_contrl
                              mestyp-shpcpr
                     CHANGING subrc.
    Perform looks like this ( in Include LV56IF0C...)
    FORM idoc_message_type_check
              TABLES   t_idoc_status  STRUCTURE bdidocstat
              USING    f_idoc_contrl  STRUCTURE edidc
                       default_mestyp LIKE edidc-mestyp
              CHANGING subrc          LIKE sy-subrc.
      IF current_mestyp <> default_mestyp.   " Here the variable default_mestyp has the value SHPCPR
        MESSAGE ID      msg-id             "Global variable
                TYPE    'E'
                NUMBER  msg-nr_wrong_function    "Global variable
                WITH    current_mestyp     "message type
                        'IDOC_INPUT_SHIPPL'"Your function module
                        f_idoc_contrl-sndprt     "Sender partner type
                        f_idoc_contrl-sndprn     "Sender number
                RAISING wrong_function_called.
    Again let me warn you that you will have to copy the entire function group V56I. Copying the function module alone will not help because there are many reusable subroutines in different includes of the function-pool.
    regards,
    Advait

  • ALE - Idoc not getting processed automatically, instead going fine in Debug

    Hello All,
    I have a problem with Inbound idoc processing.
    IDoc settings were made 'immediate processing' in WE20, and the process code is set correctly and the attached of Z-Fun. module to process the idocs to process code.
    The error in inbound side is as 'Function module not allowed: APPL_IDOC_INPUTI' 51 status. Am sure i have to do some thing with ALE settings.
    Can some body help me with correction step or sequence of steps  for this ALE process.
    Thanks & Regards, Jilan

    Hi Jilan,
    Plz follow the steps:
    ALE Configuration:
    •     WE30 - IDOC type creation
    •     WE31 - Create segment
    •     WE81 - Message type creation
    •     WE82 - Link IDOC type to Message type
    •     SE37   - Create Inbound Function Module
    •     BD51  - Maintain entry for Function Module
    •     WE57 - Maintain
    •     BD57  - Link Function Module, IDOC type and Message type
    •     WE42 – Create Inbound Process Code
    •     BD67  - Link Process code to Function Module
    •     WE20 - Create Partner Profile
    •     BD64  -  Display Distribution Model
    •     WE02 -  IDoc List, Display all Inbound/Outbound IDocs
    •     WE14 -  Outbound Processing of IDoc’s
    •     BD20 -  Inbound Processing of IDoc’s
    1st Step:   Create  a Segment  ( WE31)
             Segment is a structure for passing data in IDoc. It actually contains the IDoc data, just like the DDIC table/structure. Segment is created with all the required fields. Then Save it.  But, to actually use this Segment, you have to Release the Segment, otherwise u can’t use the Segment, by menu, EDIT--> Set Release.
             Now, if you want to do some change to this Segment, u cant, unless & until u Cancel the Release, by Edit--> Cancel Release.
    2nd Step:   Create IDOC Type  ( WE30 )
            After creating the Segment, now we have to create the IDoc Type. IDOC Type is like an envelop of a letter, which contains the data inside it, & also some more information like address. IDoc type can be Basic Or Extended.
           Basic IDoc Type:  Using some SAP existing IDOC type (ex. MATMAS) or Custom IDOC type.
           Extension IDOC Type:  When we need some fields extra to an existing IDOC type, then we can extend that Basic Idoc Type by another Segment. This is called Extended idoc type
    3rd Step:   Create Message Type (WE81)
         Message Type is like the Postman for sending the Letter.
      4th Step:   Attach Message Type to the IDOC Type (WE82)
    5th Step:   Create a Function Module (SE37)
           Write the Processing logic in a Function Module.
    6th Step:   Mention the IDOC Type, i.e, 0/1/2 (BD51)
    7th Step:   Assign the Message Type, IDOC Type & Function Module (WE57)
    8th Step:   Create a Custom Process Code (WE42)
    9th Step:   Attach the Function Module to the Process Code (BD67)
    10th Step: Execute Inbound IDOC’ s (WE19)
    Example Function Module: IDOC_INPUT_ORDERS (Standard FM to create Sales Order).
    reward is useful,
    regards,
    Tanmay

  • Idocs are not processed in the right order.

    Hi,
    I face a problem that when there are a large number of IDocs (Inbound) posted the Idocs are not processed in the right order.
    Msg type: MBGMCR
    any idea how this can happen?
    what is the solution?
    br
    Karen

    No answer

  • Message type, Idoc type and process code in ALE/Idoc

    Each Idoc version(creams01 or cremas03) will have seperate process codes in Inbound process?
    Whether Message type triggers the process code or the Idoctype/idoc  triggers the process code in Inbound process?
    regards
    Message was edited by: henry

    Hi Henry,
    About your question as how should you assign seperate process code for the same message type ( with different IDoc Type )-
    In We42, the message type can be assigned to the processing code. But here you will find that along with message type there are two more fields - Message Code & Message Function.
    You can use any one these to serve your purpose.
    e.g. you can assign
    -process code P1 to message type M with Message code 1
    -process code P2 to message type M with Message code 2
    Further these process types can be configured to call separate FMs.
    Now depending on IDOC types your external system should populate the message type as well as Message code so that accordingly process code will be determined at the time of inbound processing.
    I hope it's clear & correct
    Thanks,
    Ram

  • Error:IDoc cannot be processed: Qualifier not supported.

    Hi experts,
                             I got this error when executing the idoc
    message type: dirdeb
    basic type : pexr2003
    error:Error during creation of internal payment order.
    IDoc cannot be processed: Qualifier not supported.
    Thanks
    Saravanaperumal N

    Hello,
    001     Customer Purchase Order
    002     Vendor Order
    003     Customer Inquiry
    004     Vendor Quotation
    005     Customer Contract Number
    006     Vendor Contract Number
    007     Collective Number for Quotations
    008     Last Purchase Order Number (SPEC2000 Acknowl.)
    009     Invoice Number
    010     Internal Number (Document)
    011     Referenced Document Number
    012     Delivery Note Number
    013     Internal PO Number
    014     Accounting Document
    015     Billing Document Number of Invoicing Party
    016     Number of Preceding Document
    017     Assignment Number
    018     Customer Order Number
    019     ISR Number
    020     Invoice List Number
    021     ID for Cost Assignment
    022     Payment Document Number
    023     Banker's Acceptance
    024     Matured Certificate of Deposit (CD)
    025     Loan
    026     Check Number
    027     Foreign Exchange Contract Number
    028     Credit Memo
    029     Payment Advice Note Number
    030     Original Purchase Order Number (ALE)
    031     Return Leg Number
    032     Reference Bank
    033     Third-Party Reference Number
    034     Reference Number of Beneficiary's Bank
    035     Message Reference
    036     Credit Card Number
    037     Statement Number
    038     Account Statement No. (Deposit No.)
    039     Account Statement No. (Deposit Seq. No)
    040     Payee Code
    041     MICR Line
    042     Imported Line
    043     Vendor Contract Number
    044     Ship-To Party's PO Order
    045     Cost Center
    046     Profitability Segment No.
    047     Work Breakdown Structure Object
    048     Profit Center
    049     Business Area
    050     Delivery Order
    051     Delivery Order Route Number
    052     Sequence Number
    053     Scheduling Agreement Number
    054     External Transaction
    055     Promotion Number
    056     Customer Quotation Number
    057     Customer Buying Group
    058     Customer Contract Number
    059     Check Number from Check Register
    060     JIT Call Number
    061     Internal Delivery Note Number
    062     Customer PO no. for consignment issue by ext. service agent
    063     External Delivery Note Number
    064     Goods Receipt/Issue Slip Number
    065     Repetitive Wire Nummer
    066     External Order Number
    067     Quality Notification Number
    068     External Inquiry Number
    069     Business Partner Reference Key
    070     Reference Text for Settled Items
    071     Customer ID no.
    072     Agreement Number
    073     Credit Advice Number
    074     Transfer Number
    075     Check Number
    076     Credit Posting Number
    077     Transfer number (just transferred)
    078     Delivering Profit Center
    079     Batch Number
    080     Certificate Profile
    081     Collective Daily Delivery Note
    082     Summarized JIT call
    083     External Delivering Plant
    084     Tax Number Tax Office §14
    085     KANBAN ID
    086     Kanban Control Cycle
    087     Reference Document Number Billing Doc.
    101     Resale Invoice No.
    102     Resale Ship and Debit Agreement No.
    103     Customer Claim Reference Number
    104     Design Registration Number
    105     TPOP Order Number
    106     TPOP Reference Order Number
    111     Partner Business Area
    APY     Approval Year of Official Document Numbers
    APN     Registration Number of Official Document Numbers
    SNC     Serial Number of Statement
    These are all the Value range for qualifier, use which one suits your requirement
    Regards,
    Abhishek

  • Idoc WPUWBW: Status 51 - IDoc not fully processed

    Hi All!
    Hi All!
    This is regarding Goods Moment.
    In Quality, Idoc is successfully generated at POSDM system and also in ECC system.
    In Production, Idoc is successfully generated at POSDM, but in ECC it is failed (Idoc WPUWBW: Status 51-IDoc not fully processed).
    So, at WPER it is showing as In deficit of stock. But stock is available.
    Kindly suggest me how to close this issue.
    Note: PFA Below. Its the screenshot of the error at WPER.
    With Regards,
    Yarnagula Sudhir.

    Dear Venu
    Difficult to answer with this limited information. If you share some more info will be easier to help
    regards
    Manish

  • Transaction using which an IDOC can be processed in Foreground mode

    Hi,
    Can you please suggest a transaction using which an IDOC can be processed in Foreground mode? We have seen that from SAP Inbox, it is possible to navigate and process IDOC in Foreground mode. We are looking for a Transaction code which will allow us to do the same.
    We tried using BD87 but we did not find an option which allows processing an IDOC in Foreground mode.
    Kindly help.
    Regards

    BD87 should let you do this.
    Execute BD87 to select the failed IDOC.
    click on the line with the failed IDOC, then use menu option Edit -> Restrict and Process.
    On the next screen the IDOC number will show, and un-check the "Bkgd processing" check box at the bottom of the screen and execute.
    The next screen will display the status record for the IDOC, then select menu entry Edit ->Process -> Foreground Processing.
    This will then reprocess the IDOC in foreground mode.

  • Idoc to be processed only when vl32n has been posted

    Hi All,
    I want the IDOC to be processed only when VL32N is been posted
    Regards
    Amey Kulkarni

    a

  • Lock an Idoc to avoid processing twice

    Hello,
    I have a question on how I can avoid processing an idoc which is already in process.
    Scenario: The Idoc is processed manually. Within a second gap, a batch program also processed the same idoc.
    Result: 2 subsequent LUW Idocs got created.
    It has to be avoided.
    Logic : Once the Idoc processing it started, function module ZIDOC_INPUT_SHIPMENT_LUW is triggered. This calls ZETM_OPTIMIZED_SHIPMENT_LUW function module which in turn calls ZETM_PROCESS_SO_LUW. For event ACPD, if shipment does not exist then check if delivery exists. If delivery does not exist, create delivery. If delivery is created, then call function module IDOC_INBOUND_WRITE_TO_DB. Then call function module IDOC_START_INBOUND. Idoc status set to 53.  Call function module IDOC_STATUS_WRITE_TO_DATABASE.
    For manually triggered idoc, subsequent idoc is created without delivery.
    Batch processing created delivery and then the subsequent Idoc.
    Former should not occur.
    How can I resolve it?
    Is it possible to lock the Idoc once the processing is started?
    Any alternate way?
    Appreciate your help.
    Thanks,
    Benjamin

    Hi,
    Check an idoc in we05 here you will get partner details from control record,
    for inboud IDOC your system will be reciver system, get those partner details from edidc fill the same details in both sender and reciver.
    or get an idoc number form your system inboud or outbound Idoc then goto se11 and table EDIDC enter idoc number you will get the control record values for that idoc if it is inboud idoc just chsnge the sender information and copy same values as in reciver for outboud vice versa, just change the parter details..
    hope this helps you.
    Thanks
    Pavan

Maybe you are looking for