IDOC number update in processing log

Hi
My problem is when I run VL02N, although it updates the NAST table with a record dynamically , it does not update NAST-CMFPNR field, hence I cannot find the updated idoc number in the processing log  acceding to NAST-OBJKY.It was showing previuos idoc number.
Thanks

Hello,
Did you try to disable and then enabled CDC capture for the database? How about restart the SQL Server Agent?
If the issue presists, please post the more information in the SQL Server error log file for further analysis.
Regards,
Fanny Liu

Similar Messages

  • IDoc Number of that Document

    Hi Guru's,
    I want to know the Table/Field from which i can get the IDoc number that was created for that particular document. I know we can see the IDoc number in the 'Processing Log' from the Ouput screen but don't know where that info is stored.
    thanks,
    Kumar.

    Hi,
    May check for fm
    GET_IDOCNR_FROM_OBJECT
    a®

  • IDOC number related to the delivery

    Hi All,
    I have issue regarding finding out IDOC related to a delivery.
    When the output is processed for a delivery, idoc gets created. Now this idoc number gets stored in the EDIDC table. In delivery one can get the related idoc number by checking the processing logs for the output type.
    Is there any specific FM which can give me the idoc number of the latest processed output type for that delivery. I have delivery number and output type.
    Thanking in advance.
    Regards,
    Shahu

    Hi..
    I think need to add further to my question.
    I have an interface progra in which I am sending IDOC details related to the delivery.
    Now in this interface program, I have delivery no and the processed output type. Using this how can get the IDOC no. I cannot go to EDIDC to get the idoc no as it will be performance intensive or to any transaction. I need to code here to somehow get the idoc number using this delivery and output type.
    I am trying the following approach but could not implement it so far.
    In delivery is I go to header>output>check the processed output type -->processing log --> the idoc number  will be present in this log.
    I am trying to code in the interface program to read this idoc number present in processing log.
    Is there any way I can achive this.
    regards,
    Shahu
    Regards,
    Shahu

  • Getting processing log for our custom output triggering FM?

    Hello,
    VA02 > Extras>Header>Output>Edit --- Triggering an custom IDOC
    Stadnard SAP output programs shows IDOC number on output processing log. But, our custom programs/FMs the one we use to trigger on order IDOC, don't show the processing log. How to get this processing log for custom FMs just like standard SAP?
    Thank you

    Hello
    I am sending my custom IDOC by using FM  'MASTER_IDOC_DISTRIBUTE', if it went well (sending successfully - status is '03') in next step am using PERFORM FILL_NAST_PROTOCOL(ROIKCALE) routine.
    But, when i checked the PROCESSING LOG of the associated green latest item in VA02/03>Extras>OP>Header>Edit....am getting a message that "No processing log exists"
    How to get/see my IDOC #?
    when i saw the F1, it says, "System logging has been de-activated for the selected output type (use settings in Customizing for current application for the selected output type)"
    When i checked the settings in NACE (and then clicking lense), they are fine.
    Am i seeing correctly to get/know the generated IDOC #?
    Thank you

  • Updating processing log for sales order header output

    I want to prevent a custom sales order confirmation from printing when the order has not been approved.  When the user requests the form to print in the background, I want to update the processing log to have a red light and a message indicating the order has not been approved, so it cannot be printed.  When I pass an error message to the protocol processing, the update is terminated and my changes to the sales order are lost.  Is there a way to update the processing log, show the red light, and not get the hard error? 
    Thank you in advance. 
    Jay

    Setting the return code after the protocol update did the trick.

  • Message Processing Log

    Hello,
    I have a message processing (outbound idoc in MIRO) performed by a custom subroutine. How can I add a detail processing log so it can be seen in the output screen (MIRO->Go to->Message->Header->Process Log)?
    Thank you,
    Leon

    Leon,
    In your custom subroutine, give all your messages as information messages, as many as you want. These will be displayed as a part of the processing log of the message output.
    As the program gets executed in the background, you should not see it on the screen.
    I just figured out that you can NAST_PROTOCOL_UPDATE function to update the processing log with all the information messages you want.
    Regards,
    Ravi
    note : Please close the thread, if this resolves the issues.
    Message was edited by: Ravikumar Allampallam

  • Write processing log for custom output type

    Hi,
      I have defined a new output type at delivery header level . This is processed using a special function and on processing moves  stock from unrestricted to a order special stock.
    I need to update the "processing log" of the output with the material document number. Can any one please let me know how I can write to this "processing log" of the output?
    Thanks in advance.
    Regards.
    Hari.

    Use function NAST_PROTOCOL_UPDATE:
    * No orders found
        wa_msgv_1 = nast-objky+0(10).
        CALL FUNCTION 'NAST_PROTOCOL_UPDATE'
          EXPORTING
            msg_arbgb = c_msgtype
            msg_nr    = 30
            msg_ty    = 'S'
            msg_v1    = 'No orders found for delivery'
            msg_v2    = wa_msgv_1
          EXCEPTIONS
            OTHERS    = 1.

  • How to read the processing log of message control ....

    Hi,
        I would like to find the idoc # generated by message control ...
        The input is delivery number that uses message control....
        In the delivery header output part, we can see the idoc # by pressing the
        processing log button, but i don't know how to get this log in ABAP program
        any good suggestions? Thanks

    Hi,
    Do you mean to read the mail content in R/3 inbox or UWL..?
    If in R/3 then SBWP transaction Unread Documents..
    If in UWL see notifications part.
    Please if this does not solve your problem> please elaborate on your problem
    Regards
    Sai

  • Message with IDOC number, created by LSMW, missing in job log in SM37

    Hi gurus,
    We have a temporary interface which uses LSMW to create IDOCs and update in SAP. It's used for materials, BOMs and document info records. In LSMW we have defined standard message types MATMAS_BAPI, BOMMAT and DOCUMENT_LOAD for the IDOCs. All these have the same problem.
    A background job runs and starts LSMW. In the job log in SM37 I want to see which IDOCs were created. For some reason this is different in my development system and my test system, and as far as I know all settings should be the same. In the test system LSMW creates more message lines in the job log, than it does in the dev system. Message number E0-097 is "IDOC XXXX added", and this is missing in the dev system.
    This is what it looks like in the dev system:
    Data transfer started for object 'MATMAS' (project 'X', subobject 'Y')             /SAPDMC/LSMW   501    I
    Import program executed successfully                                                             /SAPDMC/LSMW   509    I
    File 'XXX.lsmw.read' exists                                                                               /SAPDMC/LSMW   502    I
    Conversion program executed successfully                                                    /SAPDMC/LSMW   513    I
    Data transfer terminated for object 'MATMAS' (project 'X', subproject 'Y')       /SAPDMC/LSMW  516    I
    And this is what it looks like in the test system. More information, which is exactly what I want in dev system too:
    Data transfer started for object 'MATMAS' (project 'X', subobject 'Y')             /SAPDMC/LSMW   501    I
    Import program executed successfully                                                             /SAPDMC/LSMW  509    I
    File 'XXX.lsmw.read' exists                                                                               /SAPDMC/LSMW  502    I
    Conversion program executed successfully                                                    /SAPDMC/LSMW  513    I
    File 'XXX.lsmw.conv' exists                                                                              /SAPDMC/LSMW   502   I
    IDoc '0000000002489289' added                                                                      E0                         097   S
    File 'XXX.lsmw.conv' transferred for IDoc generation                                      /SAPDMC/LSMW   812   I
    Data transfer terminated for object 'MATMAS' (project 'X', subproject 'Y')      /SAPDMC/LSMW   516   I
    In both cases the IDOC is created and update works fine.
    My only issue is that I can't see the IDOC number in the dev system. I know I can get the IDOC number in WE02, but in this case we have program logic which reads the job log to be able to check IDOC status before sending OK message back to the other side of the interface.
    I hope any of you can have an idea how I can update somewhere to get message E0-097 with IDOC number into the log.
    Regards,
    Lisbeth

    Hi Arun,
    If you want to show your messages in the job log you have to use the MESSAGE statement. In case you use WRITE statements an output list be created which can be found in the spool (there is an icon to go to the spool directly).
    Regards,
    John.

  • Processing log not getting updated for send immediatly

    Hi,
    I have a custom output type and a Custom function module for issueing the output for delivery, my prob is that it processing log is getting updated for the send in batch and other options but it is not getting updated for the SEND IMMEDIATLY, I am using the same FM for the Output issue I am checking if they have selected output type as 4 if yes, I am calling a FM in perform by saying
    PERFORM xxxxxxxx ON COMMIT
    and in the perform I am calling a FM
    CALL FUNCTION  xxxxxxxxx in BACKGROUND TASK  AS A SEPARATE TASK,
    the functioanlity of issueing the output is working but the Processing log is not getting updated.
    What might be the problem ? it is getting updated for  Send in batch but not for except 4.

    I am updating Log using this form
    at every step I am collecting the messages and passing them to this form.
    FORM update_nast_log  USING   p_msgid
                                  p_msgnr
                                  p_msgty
                                  p_msgv1
                                  p_msgv2
                                  p_msgv3
                                  p_msgv4.
    * Local data declaration
      DATA: lv_msgid LIKE sy-msgid,
            lv_msgnr LIKE sy-msgno,
            lv_msgty LIKE sy-msgty,
            lv_msgv1 LIKE sy-msgv1,
            lv_msgv2 LIKE sy-msgv2,
            lv_msgv3 LIKE sy-msgv3,
            lv_msgv4 LIKE sy-msgv4.
    * clear all the local variables
      CLEAR:lv_msgid,
            lv_msgnr,
            lv_msgty,
            lv_msgv1,
            lv_msgv2,
            lv_msgv3,
            lv_msgv4.
    * move message ID,number,msg type and the messsages
    *     to local variables
      MOVE: p_msgid TO lv_msgid,
            p_msgnr TO lv_msgnr,
            p_msgty TO lv_msgty,
            p_msgv1 TO lv_msgv1,
            p_msgv2 TO lv_msgv2,
            p_msgv3 TO lv_msgv3,
            p_msgv4 TO lv_msgv4.
    * Update nast table using nast protocol update
      CALL FUNCTION 'NAST_PROTOCOL_UPDATE'
        EXPORTING
          msg_arbgb = lv_msgid
          msg_nr    = lv_msgnr
          msg_ty    = lv_msgty
          msg_v1    = lv_msgv1
          msg_v2    = lv_msgv2
          msg_v3    = lv_msgv3
          msg_v4    = lv_msgv4.
    ENDFORM.                    " UPDATE_NAST_LOG

  • JDBC to IDOC scenario and database update the idoc number

    Hi SDNers,
    I am willing to pull data from a database table to generate IDOC in SAP and want to update the  DATABASE with IDOC number in a single scenario.
    Kindly suggest ?
    REGARDS!!
    SSR

    Hi,
        Please keep in mind that the idoc no generated in PI will be different than the one generated in SAP...for idoc...
    the correlation between the idocs in both systems is the message id...
    HTH
    Rajesh

  • No processing log generated from the output type for the IDOC

    Dear experts,
    the output type which is triggered with a transmission medium Special Function has not generated any IDOC.
    The question is what is the role of a Special function and EDI transmission.
    In some cases the system has generated an IDOC and some cases not. The output is pickedup automatically, but
    does not always trigger an IDOC, Thats is the issue I am facing.
    Therefore in cases where there was no IDOC created there is no processing log generated.
    KIndly help.

    The status is green, and when I try to show the IDOC it  doesnt show and no processing log.
    The same output is processed for a delivery and it creates a IDOC but sometimes it doesnt.

  • To get IDOC number when running MASTER_IDOC_DISTRIBUTE in update task.

    Hi ,
    I am running 'MASTER_IDOC_DISTRIBUTE' Func Module for creating FIDCC2 message type IDOC in UPDATE TASK. I am not getting IDOC number of the created IDOC in this case.
    Can anyone pls update me how do I get it?
    Thanks,
    Prabhu
    Note: Useful answers will be rewarded.........

    I found the resolution....
    Thanks all.

  • Writing spool number into Processing log at VL02N

    Hi ,
    How we can write spool number into Processing log of VL02N by  ABAP coding.
    In Functional side, 'No processing log selected' check box is unchecked at NACE in General data. Eventhough it is not writing the spool number in processing log.
    Processing log button will be in between of communicaton method and Further data buttons.
    Thanks & Regards.

    if the field is flagged and you don't get a processing log (with the spool-number in it - SAP standard does that) most likely there were problems processing the document. check in NACE whether all settings are correct and you condition records are found. for the latter go to tx. VL02N -> Extras -> Delivery Output -> Header -> Goto -> Determin. Analysis.

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

Maybe you are looking for