Error in idoc foreground processing (FB01) from SBWP Inbox

Hi all
I m trying to process the idocs in my inbox.I m encountering a problem that it process only one idoc and while trying to process any more from there it doesnot process in foreground and gives only the message that:-
<b>"Two accounts were transferred but not BSEG-HKONT"</b>
Description of msg:-
<i>Message no. F8 020
Diagnosis
Two accounts were transferred but not BSEG-HKONT.
This error also occurs if more than 1000 line items are transferred. In this case, the transferred data must be distributed across several documents.</i>
Now if i logoff the screen and again go to inbox,it again allows me to process any of the records only once.
What should i do,if i want to process as many record i want from the inbox one after other without the need to logoff from inbox.
Any clue will be appreciated.
Regards
DhanyaR Nair

Hi,
If you check the message B1 and message 120 has been used in 3 function modules
here all are pointing to RCVPRT and partner type LS
1. COMMUNICATION_IDOC_CREATE
  if idoc_created is initial and
   idoc_control-rcvprt = partner_type_ls_c.
    message a120(b1) with idoc_control-rcvprt
                    idoc_control-rcvprn
                    idoc_control-rcvpfc
                    idoc_control-mestyp
       raising receiver_not_authorized.
  endif.
2. MASTER_IDOC_DISTRIBUTE
    elseif communication_idoc_control-rcvprt = partner_type_ls_c.
      message a120(b1) with communication_idoc_control-rcvprt
                      communication_idoc_control-rcvprn
                      communication_idoc_control-rcvpfc
                      communication_idoc_control-mestyp
        raising error_in_idoc_control.
    endif.
3. ALE_IDOC_PROCESS_ERROR_OUT
    elseif resulting_idoc_control-rcvprt = partner_type_ls_c.
      message a120(b1) with resulting_idoc_control-rcvprt
                      resulting_idoc_control-rcvprn
                      resulting_idoc_control-rcvpfc
                      resulting_idoc_control-mestyp.
    endif.
aRs

Similar Messages

  • Error in IDOC-inbound processing

    HI All,
    while Posting a IDOC in Batch , i am getting an
    errot Status - 51. The Error Message is Field LFA1-SPERQ . is not an input field.But While Processing in
    WE19 i am able to Load it.
    Regards,
    Hazam

    Hi,
    Go thru this links
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400365
    http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
    Check whether you are using exact  FM.
    Thanks
    Sunil

  • Idoc inbound processing? from non-sap system?

    Hi experts,
    I'm confused with some functions below:
    IDOC_INBOUND_SYNCHRONOUS
    INBOUND_IDOC_PROCESS
    IDOC_INBOUND_SINGLE
    IDOC_INBOUND_ASYNCHRONOUS
    can you tell me what are the differences? when to use them?
    for sap outbound processing, we can only call function master_idoc_distribute to generate idoc or use message control to trigger outbound idoc. no other options, correct?
    for sap inbound processing, if we use message control for automatical posting, we have process code which read  the inbound idoc file and do the sap posting. when to use those functions above?
    does the middlewares like seeburger, GIS call those functions to generate idocs at SAP side?
    in what scenarios can we use those functions? read directly non-sap file into sap internal table then call the functions to create inbound idoc? how about the posting? call inbound processe code function after the functions above?
    in case the interface between sap and legacy system is using above functions to build inbound idoc in sap and sap use process code for inbound posing, sap can monitor all inbound process using idoc, but how can the legacy system mornitor the interface?
    Thanks.
    Legend.
    Edited by: legend li on Dec 21, 2010 4:58 PM
    Edited by: legend li on Dec 21, 2010 5:40 PM

    Hi Christophe,
    Awesome!!!!!! it worked, You are the best.
    I could able to create a sales order in CRM,but below are the valid data I passed in the respective segment fields.Except for first 3 values rest all did not get reflected in teh Sales order.I feel i am missing some qualifiers.
    Can you kindly share the  IDoc data to be passed in...along with respective segments and fields:
    Segment                                                 Field
    E101CRMXIF_BUSTRANS     OBJECT_TASK         
    E101CRMXIF_BUSTRANS     PROCESS_TYPE
    E101CRMXIF_BUSTRANS     POSTING_DATE
    E101CRMXIF_PARTNER                          PARTNER_NO
    E101CRMXIF_PARTNER                RELATION_PARTNER_NO
    E101CRMXIF_ORGMAN         SALES_ORG
    E101CRMXIF_ORGMAN          DIS_CHANNEL
    E101CRMXIF_ORGMAN         DIVISION
    E101CRMXIF_SALES             PO_NUMBER_SOLD
    E101CRMXIF_SALES            YOUR_REF_SOLD
    E101CRMXIF_SALES            PO_NUMBER_SHIP
    E101CRMXIF_BUSTRANS_ITEM     ITEM_NUMBER
    E101CRMXIF_BUSTRANS_ITEM     ITEM_TYPE
    E101CRMXIF_BUSTRANS_ITEM     ORDERED_PRODUCT
    E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT
    E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT_ISO
    E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT
    E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT_ISO
    E101CRMXIF_SCHEDLIN_I     ORDER_QTY
    Thanks a ton in advance .
    Vijay

  • Error in a KO88 processing - Settlement from order to AuC

    Hi Experts,
    I am trying to settle an order using the transaction KO88 and the system give me the following message :
    Message Text
    Acquisition value negative in area 01.
    Technical Data
    Message type__________ E (Error)
    Message class_________ AA (Messages for Asset Accounting)
    Message number________ 617
    Message variable 1____ 01
    Message variable 2____ 
    Message variable 3____ 
    Message variable 4____ 000000040053-0000
    \i need to know how to correct that and settle the order, \i finished the settlement for more than 100 order and only this ones has error
    Regards,
    Marcos

    Hi,
    I have faced this issue earlier. You have 2 options in this case.
    Option 1 : As Ajay said, change the config to allow negative book value in the depn area. However i don't suggest the same because this will do away with an important validation , that the book value should never be negative. This happened only in exception  cases.
    Option 2 : You should mark the Asset master to allow negative values in the Tab Depn areas. Double click on the Depn area, and check the option " Negative values allowed ". With this, only for the asset, negative values are allowed. In case you don't see this field, you need to change screen layout rule so that the field is visible.
    Please note once you check the negative values allowed option in the asset master, you cannot change it once you settle the Asset.
    You should check the negative values allowed indicator for the AUC concerned.
    Njoy
    Siva

  • IDOC Inboun processing success but no record posted to table

    Hi,
       We are performing ALE refresh in RCD221 (development system). The ALE IDOCS are extracted for HR area with Message class as HRMD_A, the IDOCS are processed successfully from the sending system (RCB) and reaches the receving system RCD221. While we process the inbound IDOCS in RCD221 records are not getting posted in the table, however the IDOC status is shown as successful (53). This is happening when we are processing the data for object type 'P'.
    Regards,
    Bharath Mohan B.

    RFC destinations, Logical systems, and then Partner profiles needs to be maintained. and You need to create the Distribution model  in sender system.
    Partner profiles maintained in both the systems, soure Outbound properties
    Target Inbound properties.
    if you have two clients in system it will be easily you can check.

  • AES filing error - Idoc Outbound Processing: EDI number cannot be compiled

    Hi Gurus,
    We are configuring the AES filing.
    we've done the EDI  configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
    Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
    All suggestions are welcome.........
    Thanks in Advance.

    Hi Shiva,
    Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
    Cheers
    Harsha

  • Error : Pre Settings for IDoc inbound processing are missing error

    Hi Experts,
    There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
    Thanks in advance.
    Madhurima.

    I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
    [iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299]

  • IDoc to Soap, with BPM - Permanent error in BPE inbound processing

    Hi Experts,
    IDoc to Soap, with BPM - > Permanent error in BPE inbound processing
    How to rectify this any issue???
    Thanks-
    sk

    Hi,
    The inbound processing encountered a permanent error and the queue therefore stopped.
    The error message "Permanent error in BPE inbound processing" may be caused by the following:
    - At the start or when you process a process instance, the inbound processing encounters an exception that was not handled. This exception is triggered, for example, by a transformation step, a synchronous send step or a control step but it was not caught in an exception handler branch. If the exception that was not handled occurs in the first transaction of the started process instance, the system does not write the process instance to the database but it sets the queue that has this error message to the error status.
    Refer to the help in Note 1082099
    - The inbound processing triggers this error if the correlation evaluation shows that a message should be delivered to a process instance that has the status "error". Since delivery to process instances that contain errors is not permitted, the queue is stopped.
    Use the simulation of the message delivery in the detail view of the relevant queue LUW to determine the relevant process instance for the affected message and use transaction SXMB_MONI_BPE "Continue Process Following Error" (or transaction SWF_XI_SWPR) to continue. If you cannot continue the process instance, check whether you can logically delete the instance. In this case, use the method that is described in Note 807906 to logically delete a process instance.
    Check whether your system contains other process instances that have errors in order to detect similar problems. Use transaction SXMB_MONI_BPE "Continue Process Following Error" or transaction SWF_XI_SWPR.
    Use the report RSWF_CRL_MAINTAIN to check all of the correlation instances in question or the relevant process instances that you can reach using "Display Work Item".
    - Messages that cannot be delivered because no correlation instance can be found may lead to the error that is mentioned here. Check whether the causes that are outlined in Note 1094028 affect your case.
    Hope this will help you.
    Regards
    Aashish Sinha
    PS : reward points if helpful.

  • Error During IDoc Processing

    Hi friends,
    i want to transfer data in between two systems.
    i have created my own message type = ZSACH
    Basic type  = ZSACH1
    segement = ZSACH
    model view = new_model
    when i am execuiting this IDOC by using the program i am getting the error as
    EDI: Syntax error in IDoc (segment cannot be identified)
    here i am giving the coding what i have write in my program
    parameters :p_logsys like tbdlst-logsys.
    data : gen_segment like edidd-segnam value 'ZSACH1'.
    data : control_dat like edidc,
           control_dat1 like edidd,
          gen_data like zsach .
    tables : zsach1.
    data: begin of inttab occurs 0,
            lname type zsach1-lname,
            fname type zsach1-fname,
          end of inttab.
    data :
          int_edidd like edidd occurs 0 with header line,
          int_edidc like edidc occurs 0 with header line.
    select * from zsach1 into corresponding fields of table inttab.
    if sy-subrc ne 0.
      message 'no data' type 'I'.
      exit.
    endif.
    control_dat-mestyp = 'ZSACH'.
    control_dat-idoctp = 'ZSACH1'.
    control_dat1-segnam = 'ZSACH'.
    control_dat-rcvprt = 'LS'.
    control_dat-rcvprn =  p_logsys.
    loop at inttab.
      gen_data-lname = inttab-lname.
      gen_data-fname = inttab-fname.
      int_edidd-segnam = gen_segment.
      int_edidd-sdata = gen_data.
      append int_edidd.
    endloop.
    call function 'MASTER_IDOC_DISTRIBUTE'
      exporting
        master_idoc_control                  = control_dat
    *   OBJ_TYPE                             = ''
    *   CHNUM                                = ''
      tables
        communication_idoc_control           = int_edidc
        master_idoc_data                     = int_edidd
    exceptions
       error_in_idoc_control                = 1
       error_writing_idoc_status            = 2
       error_in_idoc_data                   = 3
       sending_logical_system_unknown       = 4
       others                               = 5
    if sy-subrc <> 0.
      message id sy-msgid type sy-msgty number sy-msgno.
    else.
      loop at int_edidc.
        write :/ 'IDOC GENERATED',int_edidc-docnum.
      endloop.
      commit work.
    endif.
    <Added code tags>
    can anyone give better solution for this error..
    i have searched in SDN but i can't get the better document
    thanks in advance.
    Regards,
    kk
    Moderator Message: Please use "code tags" to format your code.
    Edited by: Suhas Saha on Nov 9, 2011 12:59 PM

    Hello kk,
    It is very clear from the error message
    EDI: Syntax error in IDoc (segment cannot be identified)
    that there is some problem with the segment name.
    When i look at your code snippet i can see there is a mismatch in the segment names passed in the IDoc control rec & the data rec.
    control_dat1-segnam = 'ZSACH'.
    int_edidd-segnam = gen_segment. "gen_segment like edidd-segnam value 'ZSACH1'
    BR,
    Suhas
    PS: Before searching in SDN try to put-in some self-effort, saves time actually

  • Error when running the OWB process flow from the shell script

    Hi,
    I am able to deploy the process flow succesfully but when I execute the process flow from the shell script,I am getting the following error.Previously it worked fine.
    I had to make some chnage in the IP address,so i had to deploy again.
    Connected.
    SQL> @/oracle/product/owb92028/owb/rtp/sql/oem_exec_template.sql OWB_RTR LOC_P_REL PROCESS P_W_SOURCE "," ","
    Elapsed: 00:00:00.00
    Elapsed: 00:00:00.01
    Stage 1: Decoding Parameters
    | location_name=LOC_P_REL
    | task_type=ProcessFlow
    | task_name=P_W_SOURCE
    Stage 2: Opening Task
    declare
    ERROR at line 1:
    ORA-01422: exact fetch returns more than requested number of rows
    ORA-06512: at "OWB_RTR.WB_RT_API_EXEC", line 17
    ORA-06512: at "OWB_RTR.WB_RT_API_EXEC", line 137
    ORA-06512: at "OWB_RTR.WB_RT_API_EXEC", line 164
    ORA-06512: at line 205
    Thanks in advance.
    Vinay

    Hi Kamal and kanakam kolla,
    This is just to let you know that,I solved my problem little differently by creating a new location and deployed the process flow.Now my process flow is working fine when i call from the shell script.What i see is that, it does not update properly when we update and redeploy the process flow.So far this is the work arround i could think off and i succesfully tested this.
    Thank you Kamal and kanakam kolla,for giving a thought towards my problem.
    Thanks
    Vinay

  • ADM Error processing results from query: Error: Index 0 out of range

    11.1.2.1
    When running quite a large book, we are getting the following error:
    ADM Error processing results from query: Error: Index 0 out of range
    The individual reports in the books are running fine.
    PS.  The report books that are giving this error run fine on 9.3.1
    Could this be a time-out issue and how do we resolve it?

    what is background datasource Essbase or HFM
    do you have lot of data in pov please try below
    >Do you have pov prompt
    >increase jvm heap size for report server in reporting server
    >Fr log files has some more detail

  • Timeout error calling a Business Process from another Business Process

    Hi to all,
    How can I call a Business Process (BP2) from another Business Process (BP1) and wait for the response before other things are performed? I'm trying to call from BP1 in a synchronous step the process BP2; the first step of BP2 is an Open S/A Bridge and, after a transformation, a Close S/A Bridge, but no response returns to BP1 till a timeout error.
    Thank you very much,
    Antonio

    I did some changes and the error now I am getting is,
    ===========================================================
    Error : null oracle.jsp.JspServlet.internalService(JspServlet.java:186)oracle.jsp.JspServlet.service(JspServlet.java:156)javax.servlet.http.HttpServlet.service(HttpServlet.java:588)org.apache.jserv.JServConnection.processRequest(JServConnection.java:456)org.apache.jserv.JServConnection.run(JServConnection.java:294)java.lang.Thread.run(Thread.java:534)
    Error : oa_html._Text__Button__Lat._jspService(_Text__Button__Lat.java:712)oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119)oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:417)oracle.jsp.JspServlet.doDispatch(JspServlet.java:267)oracle.jsp.JspServlet.internalService(JspServlet.java:186)
    ============================================================
    Does the middle tier need to be bounced?
    Thanks

  • Error while executing the Process chain

    Hi Friends,
    The process chain that I scheduled is getting failed at the Infopackage loading stage.
    On checking the diplay message, I found the following log:
    Cannot stage requested data for datasource
    Error in source system
    I activated the datasource in source system, then replicated the same and tried to load data.
    But the issue remains the same.
    I checked in RSA7. The status corresponding to this datasource is in yellow status.
    Can I delete this entry and try again?
    Please suggest.
    Thanks in advance.
    Surjit P

    Hi,
    /people/mona.kapur/blog/2008/01/14/process-chain-errors
    Deadlock
    http://help.sap.com/saphelp_nw04s/helpdata/en/2e/44934257a5c86ae10000000a155106/frameset.htm
    Dead Locks
    2. Error in unit conversion
    Units of measure
    3.Error 1 in update
    When Src file is already open or not accessible.
    4.Processing no data
    theres no data selected after extraction
    5.Caller 70 missing
    "• This error normally occurs whenever BW encounters error and is not able to classify them. There could be multiple reasons for the same
    1) Whenever we are loading the Master Data for the first time, it creates SID’s. If system is unable to create SIDs for the records in the Data packet, we can get this error message.
    2) If the Indexes of the cube are not deleted, then it may happen that the system may give the caller 70 error.
    3)Whenever we are trying to load the Transactional data which has master data as one of the Characteristics and the value does not exist in Master Data table we get this error. System can have difficultly in creating SIDs for the Master Data and also load the transactional data.
    4) If ODS activation is taking place and at the same time there is another ODS activation running parallel then in that case it may happen that the system may classify the error as caller 70. As there were no processes free for that ODS Activation.
    5) It also occurs whenever there is a Read/Write occurring in the Active Data Table of ODS. For example if activation is happening for an ODS and at the same time the data loading is also taking place to the same ODS, then system may classify the error as caller 70.
    6) It is a system error which can be seen under
    the “Status” tab in the Job Over View.
    solution:
    "• If the Master Data is getting loaded for the first time then in that case we can reduce the Data Package size and load the Info Package. Processing sometimes is based on the size of Data Package. Hence we can reduce the data package size and then reload the data again. We can also try to split the data load into different data loads
    • If the error occurs in the cube load then we can try to delete the indexes of the cube and then reload the data again.
    • If we are trying to load the Transactional and Master Data together and this error occurs then we can reduce the size of the Data Package and try reloading, as system may be finding it difficult to create SID’s and load data at the same time. Or we can load the Master Data first and then load Tranactional Data
    • If the error is happening while ODS activation cause of no processes free, or available for processing the ODS activation, then we can define processes in the T Code RSCUSTA2.
    • If error is occurring due to Read/Write in ODS then we need to make changes in the schedule time of the data loading.
    • Once we are sure that the data has not been extracted completely, we can then go ahead and delete the red request from the manage tab in the InfoProvider. Re-trigger the InfoPackage again.
    • Monitor the load for successful completion, and complete the further loads if any in the Process Chain.
    6.Idoc not processed completely.
    Here the request remains yellow (in process) and with the same details (as seen in the details tab of the monitor) for an abnormally long time. Many-a-times, the port for communication is not open and re-starting the load helps. For long running jobs, it may not be advisable to restart the extraction
    Contact the BASIS administrator to push the IDOC.
    look into these links:
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    For common data load errors check this link:
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    Majority of the issues will be based on these things only..
    Hope the following links will give u a clear idea about process chains and clear ur doubts.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/sap-teched-03/using%20process%20chains%20in%20sap%20business%20information%20warehouse
    Business Intelligence Old Forum (Read Only Archive)
    http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/c08b3baaa59649e10000000a11402f/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8da0cd90-0201-0010-2d9a-abab69f10045
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/19683495-0501-0010-4381-b31db6ece1e9
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/36693695-0501-0010-698a-a015c6aac9e1
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9936e790-0201-0010-f185-89d0377639db
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3507aa90-0201-0010-6891-d7df8c4722f7
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/263de690-0201-0010-bc9f-b65b3e7ba11c
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    Siggi's weblogs for data load error and how to restart process chain
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    Hope this helps.
    pls award me some points
    thanks.
    Thanks

  • RFC error in idoc to file scenario in PI 7.0

    Hi Experts,
       I am getting a RFC error message like this below
    :u201D  RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Z_XI_SEND_MAIL in remote system (RfcClient[RFC_REJECTION_MAIL]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught.u201D
    Here  Z_XI_SEND_MAIL is a customised function module which is calling some classes. This function module is responsible for sending emails to a group of people.  This function module is working fine in acceptance server and development server but throwing exception in production. Thus the users are unable to receive emails. There has been no code changes in the function module. Idocs are being triggrred from sap r/3 system into XI, then being processed by a BPM, finally RFC   (Z_XI_SEND_MAIL )   is being called to send email messages. SXMB_MONI  is showing that the email message is being send to the RFC properly but communication channel is showing the above mentioned error.
    Please suggest me what might be the reason of such errors?
    Regards
    Anupam

    Hello,
    Have you tested the production data in your acceptance system or development system for the interface?
    Is it working fine??
    It seems that the function module is generating exception, which could be due to data.
    -Rahul

  • Special Character error in IDOC

    All,
    I am trying to upload PO data using IDOC type "PORDCR1" from LSMW. All is well till I convert data. We have some speical characters in short text field at item level and even when I convert the data and display it from LSMW it looks fine, but when I processing idoc it's erroring out meaning if I have special character "Á" in IDOC during processing it's getting converted to "Á#" and it's screwing up the positions.
    What I am not able to understand is when I am displaying the converted data in segment mode in LSMW it's getting displayed perfectly without extra "#", but when I am checking errored idoc from WE05 it has this new #. Did anyone come across this issue?
    Your help will be greatly appreciated. Thanks for your time.

    Ok, the issue was with LSMW port (which was not marked as UNICODE) and because of which it's not translating special characters....

Maybe you are looking for