Process idocs in a particular order

Hi,
I have a problem where application generates multiple idocs. The idocs are dependent on each other. Now while processing it does not gets processed in a required order and hence fails.  We tried with qrfc where instead of trfc but could not control it.
How do we maintain this ordering?
Regards
Anirudha

Anyone know how to get all songs by one artist on a cd where it won't go through each cd. I'd like to hit random and it go wherever and not one cd at a time. It will random through the first cd, the second, but not random all of them at once. Does that make sense?

Similar Messages

  • Need list of Idocs for a particular Order Number

    Hello all,
    I am processing Outbound Purchase order Idocs.
    I need to know all the IDOC Numbers that got triggered for a particular Purchase Order.
    Example : for Purchase Order number 4500000001 there were 10 IDOCS that got created over the last 5 days.
    How do i get a list of all those IDOC numbers for that particular PO Number.
    Regards,
    Arun

    Hi,
    you have to check the objects relationship tables IDOCREL and SRRELROLES.
    Hereafter a simple abap, just an example on how the relationship works.
    REPORT  ZSDN_IDOCREL.
    data: lsrrelroles type srrelroles,
          lroleid     type srrelroles-roleid,
          lrole_b     type idocrel-role_b.
    parameters: pebeln TYPE ekko-ebeln OBLIGATORY default '4500015519'.
    * 1 SRRELROLES: From the Business Object Key (Purchase Order) gets the corresponding link
    SELECT roleid FROM  srrelroles into lroleid up TO 1 rows
           WHERE  objkey    = pebeln
           AND    objtype   = 'BUS2012'
           AND    roletype  = 'OUTBELEG'.
    ENDSELECT.
    check sy-subrc = 0.
    * 2 IDOCREL; From the Purchase Order link get the Idoc Link
    SELECT role_b  FROM  idocrel into lrole_b UP TO 1 ROWS
           WHERE  role_a  = lroleid.
    ENDSELECT.
    check sy-subrc = 0.
    * 3 SRRELROLES: From the Idoc Link gets the corresponding object key (Idoc Number)
    SELECT  * FROM  srrelroles into lsrrelroles UP TO 1 ROWS
           WHERE  roleid  = lrole_b.
    ENDSELECT.
    check sy-subrc = 0.
    write:/ 'Purchase Order:', pebeln.
    write:/ 'Outbound Idoc :', lsrrelroles-objkey.
    Regards,
    Andrea

  • IDoc Configuration for Production Order Creation and Change

    Hi All,
    Please Help me out for IDoc Configuration for Production Order Creation and Change
    I have found the IDoc for Production Order
    Messgae Type : LOIPRO and IDoc type : LOIPRO01
    Actually my requirment is to send the (LOIPRO01 )IDoc from SAP R/3 to XI system ,when ever the Production Order Created and Changed,
    I have done following Configurations:
    1. RFC Destination created for XI system
    2. PORT was created for XI
    3. Partner profile created WE20 and LOIPRO01 IDoc is added in OutBound Perameter.
    I need to know how to do the followning.
    1. How do i configure the outbound Production order idocs when Production Order is created or changed.
    2. in NACE (Output control) which is the Application for Production Order.
    3. How can I set IDoc as output Type for Production Order Creation.
    Thanks in advance
    Dhanabal T

    Hi Michal,
    I know that it is the old thread but still want to get clarified from you out of curiosity.
    Unlike other IDOC, i actiavated change pointers for LOIPRO
    1.message and idoc type is linked
    2.function module , message type , idoc type is linked
    function module used is CLOI_MASTERIDOC_CREATE_LOIPRO
    3.BD64, distribution model is created and distributed
    4. port and partner profile is in place.
    5. IDOC is not getting generated after creating the process order.
    do we need to activate the change documents for the message type in BD52,
    if yes can you please provide the object types for the same.
    or i am missing something else. please guide me in this regards.
    Thanks in advance for your time.
    S.Janagar

  • Process Code for Outbound Production Order??

    Does anybody know the Process Code for Outbound Production Order??
    BASIC Type : LOIPRO01
    Message Type : LOIPRO
    Regards,
    Ravi

    Hi Everybody.
    There's no standard process code for LOIPRO Outbound Idocs.
    This Idocs are threated as master data info, and could only be automatically generated by Data Distribution Model.
    BD64.
    Anyway, you can define your own Outbound Process Code in WE41 using CLOI_MASTERIDOC_CREATE_LOIPRO FM.
    You can choose.
    Regards.
    Albert.

  • Trigger an Idoc when a sale order is been opened in VA02 & saved

    Hi Experts
         I have a requirement to trigger an Idoc when a sale order is been opened in VA02 transaction and saved.
    Now that I have attained the same through Message Control Settings and Nace out put type settings with Multiple Issuing.
    Here in the Idoc will be triggered when the user makes any changes in the order based on the NAST table entry.
    Now my requirement is that the Idoc has to be processed even if there is no changes made to the document when the user opens the sale order and clicks save.
    This is the process been carried out to re-process the Idoc.
    Now that the Idoc is triggered using the path ---> menu - extras -output - header- edit & save.
    Now that the user need to process the Idoc by just opening the order  in VA02 and  click save.
    How can this be attained ? is there any configuration for it ?
    Or is it possible to handle the same in any of the user exit ?
    the problem is the user exit save gets triggered only when there is any change in the document else it throws a msg " No changes made"

    Hi Niraj
       Thanks for your Response.
    Now that the output control works fine when there is any change made to the document.
    Now that i need to configure such a way that the output control triggers even if there is no change to the document and save   button is clicked.
    Can U please elaborate how do i make settings in VOFM-> Output Control ?
    Thanks
    Sathish

  • Processing log output for Purchase order

    Dear All,
    Iam getting some problem when iam creating an IDOC and checking in the Processing log for IDOC number.
    Actually i had created one custom idoc for Purchase order since my client need only some field and in one line for header and line item, I had done it and i can see it in sdata of EDIDD structure. When i create a Purchase order and save it an idoc number is posting and I can see this file in my physical directory indeed.
    Now when iam going into change mode of PO ME22n to see the Processing LOG, It is not showing the IDOC Number in Purchase order output processing log popup.

    The processing log will only show output based standard output control (Table NAST).
    How is your IDoc being created. Via a user exit, BADI. If so then they will not appear on the processing log.
    It is being created as a custom IDOC for which i had written a Z function module and given that in PO processing code which is ME10. When iam checking the standard IDOC for PO it is generating the IDOC in processing log as well.
    Iam just placing my code just have a look at it and suggest if any thing needs to be done.
    FUNCTION Z_IDOC_OUTPUT_ORDERS.
    ""Local Interface:
    *"  IMPORTING
    *"     VALUE(OBJECT) LIKE  NAST STRUCTURE  NAST
    *"     VALUE(CONTROL_RECORD_IN) LIKE  EDIDC STRUCTURE  EDIDC
    *"  EXPORTING
    *"     VALUE(OBJECT_TYPE) LIKE  WFAS1-ASGTP
    *"     VALUE(CONTROL_RECORD_OUT) LIKE  EDIDC STRUCTURE  EDIDC
    *"  TABLES
    *"      INT_EDIDD STRUCTURE  EDIDD
    *"  EXCEPTIONS
    *"      ERROR_MESSAGE_RECEIVED
    *"      DATA_NOT_RELEVANT_FOR_SENDING
    DATA: xdruvo.                          "Druckvorgang
    DATA: neu  VALUE '1',                  "Neudruck
          h_kappl LIKE nast-kappl,         "Hilfsfeld Applikation
          h_parvw LIKE ekpa-parvw,         "Hilfsfeld Partnerrolle
          h_ebeln LIKE ekko-ebeln.         "Hilfsfeld Belegnummer
      CLEAR control_record_out.
       xdruvo = neu.
      h_kappl = object-kappl.
      h_ebeln = object-objky.
      h_parvw = object-parvw.
      DATA:
           LT_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE,
             L_EDIDC LIKE EDIDC,
             L_SEND_FLAG,
             W_SDATA LIKE EDIDD-SDATA.
      DATA: T_BDI_MODEL LIKE BDI_MODEL OCCURS 0 WITH HEADER LINE.
      DATA: T_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE.
      DATA: T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
      DATA: C_MESSAGE_TYPE LIKE EDIDC-MESTYP VALUE 'ZORDER'.
    *- Call function module to determine if message is to be distributed
    OBJECT_TYPE = 'BUS2012'.
      MOVE control_record_in TO control_record_out.
      CALL FUNCTION 'ALE_MODEL_DETERMINE_IF_TO_SEND'
        EXPORTING
          MESSAGE_TYPE           = C_MESSAGE_TYPE
        IMPORTING
          IDOC_MUST_BE_SENT      = L_SEND_FLAG.
       EXCEPTIONS
         OWN_SYSTEM_NOT_DEFINED = 1
         OTHERS                 = 2.
      DATA : BEGIN OF EKKO_tAB OCCURS 0,
      EBELN LIKE EKKO-EBELN,
      F1 TYPE C VALUE ',',
      BUKRS LIKE EKKO-BUKRS,
      F2 TYPE C VALUE ',',
      BSART LIKE EKKO-BSART,
      F3 TYPE C VALUE ',',
      LIFNR LIKE EKKO-LIFNR,
      F4 TYPE C VALUE ',',
      WAERS LIKE EKKO-WAERS,
      F5 TYPE C VALUE ',',
      BEDAT LIKE EKKO-BEDAT,
      F6 TYPE C VALUE ',',
      WERKS LIKE EKPO-WERKS,
      F7 TYPE C VALUE ',',
      PLIFZ LIKE EKPO-PLIFZ,
      F8 TYPE C VALUE ',',
      EBELP LIKE EKPO-EBELP,
      F9 TYPE C VALUE ',',
      MATNR LIKE EKPO-MATNR,
      F10 TYPE C VALUE ',',
      MENGE LIKE EKPO-MENGE,
      F11 TYPE C VALUE ',',
      MEINS LIKE EKPO-MEINS,
      F12 TYPE C VALUE ',',
      END OF EKKO_TAB.
      DATA SDATA1 LIKE EKKO_tAB OCCURS 0 WITH HEADER LINE.
      DATA EBELN LIKE EKKO-EBELN.
      WRITE OBJECT-OBJKY TO EBELN.
      SELECT T1EBELN T1BUKRS BSART LIFNR WAERS BEDAT  WERKS PLIFZ EBELP MATNR MENGE MEINS
      FROM EKKO AS T1
      INNER JOIN EKPO AS T2 ON T2EBELN = t1EBELN
      INTO CORRESPONDING FIELDS OF TABLE EKKO_tAB
      WHERE
    *T1~KAPPL = 'EF' AND
      T1~EBELN = EBELN.
    *T1~KSCHL = 'YEDI' .
      DATA SDATA LIKE EDIDD-SDATA.
      DATA NDATE LIKE SY-DATUM.
      DATA NMENGE(17) TYPE C.
      LOOP AT EKKO_tAB.
        WRITE EKKO_TAB-MENGE TO NMENGE.
        NDATE = EKKO_tAB-BEDAT + EKKO_tAB-PLIFZ.
        CONCATENATE  EKKO_tAB-EBELP ',' EKKO_tAB-BUKRS ',' EKKO_tAB-BSART EKKO_tAB-EBELN ',' EKKO_tAB-LIFNR ',' EKKO_tAB-BEDAT ','
        NDATE ',' EKKO_tAB-BSART EKKO_tAB-EBELN ',' EKKO_tAB-EBELN ', 0,' EKKO_tAB-MATNR ','
        NMENGE ',' EKKO_tAB-MEINS ',' EKKO_tAB-WERKS INTO SDATA.
        MOVE SDATA TO: W_SDATA, T_EDIDD-SDATA.
        MOVE 'ZORDERS' TO T_EDIDD-SEGNAM.
        APPEND T_EDIDD.
      ENDLOOP.
    *call function 'L_IDOC_SEGMENT_CREATE'
        exporting
             i_segnam = 'ZORDERS'
             i_sdata  = w_sdata
        exceptions
             others   = 1.
    *LT_EDIDC
    call function 'L_IDOC_SEND'
         tables
              t_comm_idoc           = LT_EDIDC
         exceptions
              error_distribute_idoc = 1
              others                = 2.
    *DATA T_BDI_MODEL LIKE BDI_MODEL.
    WRITE OBJECT-OBJKY TO T_BDI_MODEL.
    READ TABLE T_BDI_MODEL INDEX 1.      " maximum 1 recipient
    L_EDIDC-DIRECT = 1.
      L_EDIDC-DOCNUM = DOCNUM. "***
      L_EDIDC-RCVPRN = 'HCM_00_785'.
      L_EDIDC-RCVPOR = 'MM_PO_FILO'.
      MOVE 'ZORDER'   TO L_EDIDC-MESTYP.
      MOVE 'ZPURIDOC' TO L_EDIDC-IDOCTP.
      MOVE 'LS'      TO L_EDIDC-RCVPRT.
    MOVE T_BDI_MODEL-RCVSYSTEM TO L_EDIDC-RCVPRN.
    *MOVE-CORRESPONDING L_EDIDC TO W_EDIDC.
    *- Distribute the iDoc
    BREAK-POINT.
      CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' "IN UPDATE TASK
        EXPORTING
          MASTER_IDOC_CONTROL            = L_EDIDC
        TABLES
          COMMUNICATION_IDOC_CONTROL     = LT_EDIDC
          MASTER_IDOC_DATA               = T_EDIDD
        EXCEPTIONS
          ERROR_IN_IDOC_CONTROL          = 01
          ERROR_WRITING_IDOC_STATUS      = 02
          ERROR_IN_IDOC_DATA             = 03
          SENDING_LOGICAL_SYSTEM_UNKNOWN = 04.
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    READ TABLE LT_EDIDC INDEX 1.
      control_record_out-direct = '1'.
      CONTROL_RECORD_OUT-DOCNUM = DOCNUM. " ***
      control_record_out-serial = sy-datum.
      control_record_out-serial+8 = sy-uzeit.
      control_record_out-mestyp = LT_EDIDC-mestyp.
      control_record_out-idoctp = LT_EDIDC-idoctp.
      control_record_out-SNDPRN = 'HCM_00_786'.
      MOVE 'MM_PO_FILO' TO control_record_out-RCVPOR.
      MOVE 'LI'      TO control_record_out-SNDPRT.
      MOVE 'SAPQIS' TO control_record_out-SNDPOR.
    ENDFUNCTION.

  • While processing Idoc -error

    Hi ,
    While processing Idocs we are facing with 2 error can any one help me out.
    1.Order 123 does not exist
    2.Error in document: BKPFF $ DR0CLNT400
    Message no. RW609
    Diagnosis
    Errors occurred when checking or posting the document
    Reference type = BKPFF
    Reference key  = $
    Logical system = DR0CLNT400
    You can find the errors in the log
    Thanks and Regards
    Sri

    HI,
    Please go to transaction WE02 and look at the IDOC.
    The IDOC will have a STATUS section. when you expand it, it will give you a log with error status. Double click to look at the detailed error.
    Looking at the error it looks like you are bringing in an IDOC from another SAP system to this SAP system. The order # 123 against which IDOC is for, doesn't seem to exist in the receiving SAP system.
    Regards

  • Process IDocs in Background

    Hi,
    What is the best possible way to process an IDoc (Message type: ORDERS/ORDCHG) in background in an Interactive report.
    Thanks in advance.
    Rgds,
    AK

    Hi AK
    Here's the procedure to post IDocs in ALE inbound processing in background.
    Inbound IDocs and IDoc packets are first saved in the database. IDoc packets are split into single IDocs beforehand.
    The program RBDAPP01 later releases the saved IDocs for processing. Single IDocs can be put into packets and then processed.
    Perform the following steps:
    1. Set-up background processing (IDoc/ALE area menu):
      IDoc Interface/ALE --> Administration --> Runtime Settings --> Partner Profiles (WE20)
    Then the required setting is: In the detail screen Inbound Parameters select the option Trigger by background program.
    2. Schedule posting (ALE customizing):
    Transaction SALE --> Set-Up System Monitoring -->        Posting IDocs in Recipient System --> Schedule
    You can also process the IDocs manually by passing them to the posting function module.  In ALE Administration choose Monitoring --> Status Monitor (BD87), select the IDocs and then select Process.
    You should choose background processing, especially if large data volumes are to be distributed.  System performance is better.
    Packet Processing can be used to process individual inbound IDocs in the background.
    Dont forget to reward, if it helps ;>)
    Regards,
    Rakesh.
    Message was edited by: Rakesh

  • Unable to reduce previous year budget value for particular order

    Hi
    I am unable to reduce previous year budget value for particular order number in IM52 - process transactions - Returns
    The error msg is Overall budget less than cumulative budget
    Pls help to solve this issue.
    Regards
    P Karthikeyan

    Hi,
    Check the budget distrubuted to the internal orders values is matching with top node or parent node value or not, if that value is not matching with intenal order distrubution value then system will not accept to save.

  • IDOC Inbound Create Planned Order by Batch

    Hi Gurus,
    Anyone can give me some information regarding the Inbound IDOC for creation of planned Order? I checked the basic type LOIPLO01 and it dont have standard process code in creating planned order unlike the basic type ORDERS05 which already have the process code in creating PO which is ORDE?
    Any suggestions? Thanks!
    Best Regards,
    Jason

    Hi Mila,
    in the standard IDOC, you don't have the possibility to add a delivery block in the IDOC.
    Can you instead take a block on header level? You can add a block on header level for the sales order. We implemented a block on header level for EDI orders. This would still execute the availability check, but would block the delivery creation.
    Another option would be to cause the delivery block via special item category for EDI orders.
    Regards,
    Tanja

  • Block Production Order Creation for Particular Order Type

    Hi Experts,
    I want to disable the production order creation for a particular order type XX01 however there are some existing orders for this order type which should be processed further.
    In other words my objective is to -
    1. Block new Production order XX01 creation -
    2. Processing of order type XX01 should be possible.
    Is there standard setting available to achieve this or user exist is the only option..
    Regards,

    Hi
    You can use the user exit PPCO0006 and its function mdoule EXIT_SAPLCOZF_003 to archive that. That function module is called when the user click enter after inputting the material/plant/order type in CO01 then you just need to check the imported value CAUFVD_IMP-AUART which contains the inputted order type then rasise an error message to tell user that the order type cannot be used due to certain reason. The source code need to be written there is very simple.
    Regards.
    Leon.

  • Alert for Catching Particular Order

    Hi All,
    If any body knows how to configure Alert rule for particular Order is missed in mapping time?
    We are processing around 500 orders on daily base, so I want to send a Alert to email  for particular Order is missing. So that support team will easily  regenerate that particular Order in later. Now we are cathing message mapping error if any order missing(values is not coming) and sending to email. It confusion for support guyz for catch the particular Order in between 500 orders.
    Please let me know  how to catch this?
    Appreciate your time and catch your reward pointz.
    Thanks,

    Hi
    Follow this links
    http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm -
         Alert configuration
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2328---- [original link is broken] [original link is broken] [original link is broken]
         Alert Configuration   
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3905---- [original link is broken] [original link is broken] [original link is broken]
         Personalized alert delivery
    http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm----
         Alert Notification
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2894---- [original link is broken] [original link is broken] [original link is broken]
    Email Alerts

  • Restricting Material for particular Order type

    Dear Guru's,
    Is it possible to restrict particular material for particular order type in CO01.
    E.g. Material A is used in CO01 for order type X
           Material B is used in CO01 for order type Y
    I want to restrict CO01 should not allow production order creation of material A with order type Y.
    Regards
    Chandan.

    Hy,
    By the use of production scheduling profile you can set default order type for the required materials.But it doesn't restrict the other order type. During the manual order creation if user has select other order type then , there is no restriction.So as Mr. Shiva said put restriction over manual order creation, if possible.other option may be by using User Exit.
    Now in your case you want to restrict materials not material type. So it is quite complicated for Abaper to write code , because the for every new material Abaper has to change code.
    So there is one option by grouping perticuller materials under one production scheduler and then it is more convient for Abaper to create code for User Exit.
    Pls refer below thread which may give some more inputs  for your requirments.
    [Ugent: How to restrict a Material Type for a Specific Process Order Type;
    Regards,
    Dhaval

  • Inbound ORDERS05 IDoc - Create SD Sales Order (EDI)

    I having an issue in inbound ORDERS05 IDoc processing to create SD sales order where the sales unit of measure for the material is getting lost/replaced. We are sending sales unit of measure in the E1EDP01-MENEE field, we are also sending the material UPC in teh E1EDP19 (003) segment relying on UPC material determination rules to resolve the material for the sales order. During this process of material determination the sales unit of measure is getting lost/replaced. I know as if we send the actual SAP material in the E1EDP19 segment (no material determination required) the sales unit of measure is unchanged. In this SAP system multiple sales unit of measure are maintained for each individual UPC code. Just looking for input on where to look to resolve this, config, user exits, etc..

    I can't say for sure what you should be doing, as I don't know how you have setup your material master, or how your Customers order. We have some Customers that always want EAches, some that always want OUTers, then some who want whatever UOM is assigned to the GTIN (UPC) that they order, which could be one of several. We have our custom code in ZXVEDU03.
    Cheers, Paul.

  • Idoc number from sales order in ECC

    Hi,
    Sales order is created by processing an Idoc. Now i want to trace back the idoc number for the sales order created.
    Please let me how we can do this in ECC. I saw couple of posts stating ICON SERVICE FOR OBJECTS...i couldn't really identify that icon. In someother post i saw this can found under Environment.
    Please let me know whether there are any prerequisites for this, and how i can i achieve this in ECC?
    Thank You in Advacne
    Thank You
    Challa

    Hi Challa,
    To find which idoc created the sales order, you can do the following,
    Check for the customer PO no in the sales order.
    Then go to any other inbound idoc which is bound to create a sales order, and see in which segment is the PO number.
    Then go to WE09 and put the dates etc and then go to " Criteria for search in Data Records"
    Put the segement no in Search in segement field.
    Put the idoc field in which you see the PO number
    and put the PO no in the " for Value" field and execute.
    You will get the idoc which created the sales order.
    Let us know.
    Regards,
    SB

Maybe you are looking for