Idoc -so/billing no

hi,
in we02
message type invoic/orders -then in data record -segement -
1 here in which segment can i find billing no & sales order number
2 there are several segments like
E1EDK02 001
E1EDK02 002
E1EDK02 009 ETC  but if i try to see fields & description in WE60 for these segments getting error message not found
PL suggest

Hi,
After executing WE02 T.Code,a list will come.
Select your IDoc number and check the status whether it is red/yellow/green.
If it is in yellow then process it by using BD87 T.Code.
It will turn to red if it a failure and it will turned to green if it is successfully processed.
Double click on that idoc number in WE02.
Clcik on Data records.
Order number you can find in two data segments.
They are:
E1EDK02 002 in the field BELNR.
E1EDK01 in the same field BELNR.
Regards,
Krishna.

Similar Messages

  • IDOC and Billing Document relation

    Hi All,
    I want to know that is there any table where we can find IDOC for a Billing Document.
    Please advice.
    Thanks!
    Regards,
    Vivek Srivastava

    Hi,
    Check these tables
    EDID4
    EDIDC
    EDIDD
    Thanks and regards
    Praveen.J

  • IDOC: MM purchase order to SD scheduling agreement

    Dear experts,
    Is below scenario technically feasible?
    - Purchase order created in customer system, and sent to vendor system via IDOC
    - Scheduling Agreement created in vendor system against the received IDOC
    - Goods issue posted for delivery schedule of Scheduling Agreement, and sent to customer system via IDOC as Shipping Notification
    - Inbound Delivery created for purchase order in customer system against the received IDOC.
    - Billing created in vendor system and sent to customer system via IDOC
    - Invoice verification created in customer system against the received IDOC.
    The scenario is obviously feasible between Purchase Order-Sales Order, but I'm not sure whether it will work with Purchase Order- SD Scheduling Agreement or not. According to SAP Help, it seems that only MM Scheduling Agreement can work SD Scheduling Agreement.
    Thanks a lot,
    Duc.

    Hello Indu,
    I created two partner profiles but still receive that message above:
    Partner No: 999999
    Partner Type: LI
    Outbound parameters: ORDERS
    Outbound Options
    Message type: ORDERS
    Receiver port: A0000000006
    Pack. size: 1
    Basic type: ORDERS05
    Message Control
    Application: EF
    Message type: Z40B
    Process code: ME10
    Partner No: XXXCLNT100
    Partner Type: LS
    Inbound parameters: ORDERS
    Inbound Options
    Message type: ORDERS
    Process code: ORDE
    Kind Regards,
    Florian

  • Bill of Lading and multiple deliveries

    Hi Guru's,
    I have a question regarding Bill of Lading and deliveries. We can have multiple deliveries which are related to one Bill of Lading. Normally when I process the per delivery the DESADV IDOC but is there another way to send multiple deliveries based on the same Bill of Lading?
    Best regards,
    Guido Koopmann

    If you mean that you'd like to have multiple deliveries i one IDoc then it's not feasible. Unless you create a custom IDoc, of course. To my knowledge, there is no IDoc for bill of lading. Shipment is pretty much the only document that may include multiple deliveries.
    But if you just want to select the deliveries by BOL # and create individual DESADV IDocs for them, then it should be feasible, at least by writing a small "wrapper" ABAP report.

  • How to Extend an IDOC  !

    I have an idoc for billing  i.e INVOICE.
    How will i extend it for credit memo ?

    Hi,
    in order to extend an IDOC goto WE30 tcode.
    1) Give your basic IDOC type at the object name
    2) select the Extension radio button
    3) click on create button
    4) it asks for 3 types of extension . so give the basic IDOC type over there
    5) give description and click on continue button.
    6) so at which segment level you want to add your segment, select that particular segment and click on create segment button and place your already created segment.
    7) save and go back.
    this is the procedure of extending an IDOC
    and check this link,
    http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml
    regards,
    Archana
    Edited by: Archana Kumari on Aug 18, 2009 8:01 AM

  • RS partner function to IDoc INVOIC01

    We are creating an INVOICE01 IDoc from billing document using output determination.
    When the IDoc is created it has a partner function RS (= Invoice presented by) but the company name is misspelled. Where is this partner coming from where can I correct this? If I look at the invoice from which the Idoc was created it does not show this partner function.
    I could not find in SPRO where this comes from.
    Any help would be much appreciated.
    Thanks a lot,
    Viktor Varga

    Hi Victor,
    It generated inside FM <b>IDOC_OUTPUT_INVOIC</b> in include program LVEDFF0E.
    *-Rechnungskopf - Partnerinfo - Rechnungssteller
      PERFORM fill_e1edka1
        USING 'RS'.
    Then you can use user exits <b>EXIT_SAPLBD11_001</b> to change segment E1EDKA1. This user exits is used in FM MASTER_IDOC_DISTRIBUTE.
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

  • Display Long field Description in 2 lines in Header when using REUSE_ALV_HI

    Hi,
      I am using REUSE_ALV_HIERSEQ_LIST_DISPLAY .
    I need to have 2 lines in the header to display  long field descriptions like
    Ex   Shipment Notification Idoc or Billing Document Cancel  should appear as
    Shipment Notification       Billing Document
    Idoc                                        Cancel
    Is there a way of doing this when calling the above ALV function?
    Thanks
    Prashant

    Hi Prashanta ,
    We can give headers in ALV using short/medium/long text.
    And this comes in one line. You can use short/medium text, if possible.
    Hence , having 2 lines in the header to display long field descriptions is not possible.
    Hope this helps you.

  • Output type - Special function 8 - ARCHIV_CONNECTION_INSERT

    Hi gurus,
    I created a new Output Type with special function 8 called ZPDF in transaction NACE with application MR (invoice verification) and I added to that Output Type ZPDF our custom program called ZXXX_ARCHIVE_LINK in order to post into the MM invoice, a PDF who cames from the SD inovoice.
    The SD invoice number is recorder into the field "Referece" in the MM invoice.
    So, the program should (through the output type and the program):
    1. Read the MM invoice number generated (NAST table into NAST-OBJKY).
    2. Enter to table RBKP with MM invoice number RBKP-BELNR and get the SD invoice number: RBKP-XBLNR.
    3. Enter with SD invoice number XBLNR to table TOA01-OBJECT_ID And get TOA01-ARC_DOC_ID.
    4. Call FM ARCHIV_CONNECTION_INSERT.
    The problem here is when I post a MM inovice in MIRO transaction the system through the condition record added the ZPDF Output Type but don´t read the program ZMIC_INVOICE_PDF_ARCHIVE_LINK added to that output type. The status of the output type is green (but without any processing log). I checked the setting for the Output Type like 100 times and everything seems to be OK.
    Please this is very urgent. Any advice?
    I don´t know why SAP don´t call the program. I think the ABAP code is wrong:
    REPORT ZXXX_ARCHIVE_LINK.
    Table Declaration
    TABLES: NAST, " Message Status
    CMFP, " Storage Structure for Errors Collected
    EDIDS, " Status Record (IDoc)
    VBRK, " Billing Document: Header Data
    TOA01. " Link table 1
    TYPES: BEGIN OF TY_RBKP,
    BELNR TYPE RE_BELNR, " Document number of an invoice document
    XBLNR TYPE XBLNR1, "SAEOBJID, " Reference Document Number
    END OF TY_RBKP.
    TYPES: BEGIN OF TY_TOA01,
    OBJECT_ID TYPE SAEOBJID, " SAP ArchiveLink: Object ID (object identifier)
    ARC_DOC_ID TYPE SAEARDOID, " SAP ArchiveLink: Document ID
    END OF TY_TOA01.
    Data Declaration
    DATA: WA_BELNR TYPE RE_BELNR ,
    WA_ARC_DOC_ID TYPE TY_TOA01 , "-ARC_DOC_ID,
    WA_SAP_OBJECT LIKE SAPB-SAPOBJID," TYPE TOAOM-SAP_OBJECT ,
    ARC_DOC_ID TYPE TOAV0-ARC_DOC_ID,
    GT_RBKP TYPE STANDARD TABLE OF TY_RBKP , "WITH HEADER LINE,
    GT1_RBKP TYPE STANDARD TABLE OF TY_RBKP, " WITH HEADER LINE,
    GT_ARC_DOC_ID TYPE STANDARD TABLE OF TY_TOA01, " -ARC_DOC_ID,
    WA1_RBKP TYPE TY_RBKP ,
    WA_RBKP TYPE TY_RBKP.
    DATA: WA1_OBJECT_ID TYPE SAEOBJID.
    DATA: WA_OBJKY TYPE NA_OBJKEY,
    WA1_OBJKY TYPE RE_BELNR.
    FORM entry USING ent_retco ent_screen.
    CLEAR ent_retco.
    PERFORM ARCHIV_CONNECTION_INSERT USING nast-objky ent_retco.
    ENDFORM. "entry
    FORM ARCHIV_CONNECTION_INSERT USING objky returncode.
    * Select Reference Document Number from RBKP table
    SELECT BELNR XBLNR
    FROM RBKP
    INTO TABLE GT_RBKP
    WHERE BELNR = objky . " .WA1_OBJKY .
    IF SY-SUBRC EQ 0 .
    LOOP AT GT_RBKP INTO WA_RBKP.
    WA1_OBJECT_ID = WA_RBKP-XBLNR .
    CONCATENATE WA1_OBJECT_ID '%' INTO WA1_OBJECT_ID .
    WA_SAP_OBJECT = WA_RBKP-BELNR .
    SELECT OBJECT_ID
    ARC_DOC_ID
    FROM TOA01
    INTO TABLE GT_ARC_DOC_ID
    WHERE OBJECT_ID LIKE WA1_OBJECT_ID.
    IF SY-SUBRC EQ 0 .
    READ TABLE GT_ARC_DOC_ID INTO WA_ARC_DOC_ID INDEX 1.
    ARC_DOC_ID = WA_ARC_DOC_ID-ARC_DOC_ID.
    WA_SAP_OBJECT = WA_ARC_DOC_ID-OBJECT_ID.
    ENDIF.
    CALL Function Module:Link table operations
    CALL FUNCTION 'ARCHIV_CONNECTION_INSERT'
    EXPORTING
    ARCHIV_ID = 'Z0'
    ARC_DOC_ID = ARC_DOC_ID
    AR_DATE = SY-DATUM
    AR_OBJECT = 'MMILOGINV'
    DEL_DATE = ' '
    MANDANT = SY-MANDT
    OBJECT_ID = WA_SAP_OBJECT
    SAP_OBJECT = 'BUS2081'
    DOC_TYPE = 'PDF'
    BARCODE = ' '
    EXCEPTIONS
    ERROR_CONNECTIONTABLE = 1
    OTHERS = 2
    IF SY-SUBRC 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    CLEAR: WA_RBKP.
    ENDLOOP.
    ENDIF.
    ENDFORM.

    Hi,
    Use
    You can process a message immediately by updating the application document or you can process it at a later time. For later processing you must use the report program RSNAST00 or a corresponding application function.
    The individual possibilites are:
    Time 1: The message is processed through report program RSNAST00. This report program can be scheduled periodically or started manually.
    Time 2: As in time 1, but the message contains an earliest processing date and a requested processing time. The message is ignored by report program RSNAST00 before the requested date.
    Time 3: The message is selected and processed by application specific programs. Processing can take place online or in the background.
    Time 4: The message is processed when the application document is saved. No further processing of the message is necessary.
    Kapil

  • Regarding FM : IDOC_OUTPUT_INVOIC

    Hi All,
    Below issue is identified when FM IDOC_OUTPUT_INVOIC is used for IDOC creation billing related data.
    For some of the invoice numbers , item data is not getting populated i.e E1EDP08 is not getting populated with desired data.
    I have used breakpoint where ever E1EDP08 is populated , but program do not stop at it.
    Please let me know , what may be the cause of the issue and when is E1EDP08 populated.
    Thanks in Advance

    Hi,
    E1EDP08 - IDoc: Package data individual
    It will get populated only if you create or add values in the structure like
    shiipping ID,PACK LEVEL id,delivery,hierarchy number etc...
    Only mandatory segments of IDOC will be populated all the time.Others will be populated only if you fill those values.
    Regards,
    Subhashini

  • Special function 8 - Output Type

    Hi gurus,
    I created a new Output Type with special function 8 called ZPDF in transaction NACE with application MR (invoice verification) and I added to that Output Type ZPDF our custom program called ZXXX_ARCHIVE_LINK in order to post into the MM invoice, a PDF who cames from the SD inovoice.
    The SD invoice number is recorder into the field "Referece" in the MM invoice.
    So, the program should (through the output type and the program):
    1. Read the MM invoice number generated (NAST table into NAST-OBJKY).
    2. Enter to table RBKP with MM invoice number RBKP-BELNR and get the SD invoice number: RBKP-XBLNR.
    3. Enter with SD invoice number XBLNR to table TOA01-OBJECT_ID And get TOA01-ARC_DOC_ID.
    4. Call FM ARCHIV_CONNECTION_INSERT.
    The problem here is when I post a MM inovice in MIRO transaction the system through the condition record added the ZPDF Output Type but don´t read the program  ZMIC_INVOICE_PDF_ARCHIVE_LINK added to that output type. The status of the output type is green (but without any processing log). I checked the setting for the Output Type like 100 times and everything seems to be OK.
    <removed by moderator>. Any advice?
    I don´t know why SAP don´t call the program. I think the ABAP code is wrong:
    REPORT  ZXXX_ARCHIVE_LINK.
    Table Declaration
    TABLES: NAST,     " Message Status
            CMFP,     " Storage Structure for Errors Collected
            EDIDS,    " Status Record (IDoc)
            VBRK,     " Billing Document: Header Data
            TOA01.    " Link table 1
    TYPES: BEGIN OF TY_RBKP,
           BELNR TYPE RE_BELNR,   " Document number of an invoice document
           XBLNR TYPE XBLNR1, "SAEOBJID, " Reference Document Number
      END OF TY_RBKP.
    TYPES: BEGIN OF TY_TOA01,
      OBJECT_ID     TYPE SAEOBJID,    " SAP ArchiveLink: Object ID (object identifier)
      ARC_DOC_ID TYPE     SAEARDOID,  " SAP ArchiveLink: Document ID
      END OF TY_TOA01.
    Data Declaration
    DATA: WA_BELNR TYPE RE_BELNR ,
          WA_ARC_DOC_ID TYPE TY_TOA01 , "-ARC_DOC_ID,
          WA_SAP_OBJECT LIKE SAPB-SAPOBJID," TYPE TOAOM-SAP_OBJECT ,
          ARC_DOC_ID TYPE TOAV0-ARC_DOC_ID,
          GT_RBKP TYPE STANDARD TABLE OF TY_RBKP , "WITH HEADER LINE,
          GT1_RBKP TYPE STANDARD TABLE OF TY_RBKP, " WITH HEADER LINE,
          GT_ARC_DOC_ID TYPE STANDARD TABLE OF TY_TOA01, " -ARC_DOC_ID,
          WA1_RBKP TYPE TY_RBKP ,
          WA_RBKP TYPE TY_RBKP.
    DATA:  WA1_OBJECT_ID TYPE SAEOBJID.
    DATA: WA_OBJKY TYPE NA_OBJKEY,
          WA1_OBJKY TYPE RE_BELNR.
    FORM entry USING ent_retco ent_screen.
      CLEAR ent_retco.
      PERFORM ARCHIV_CONNECTION_INSERT USING nast-objky ent_retco.
    ENDFORM.                    "entry
    FORM ARCHIV_CONNECTION_INSERT USING objky  returncode.
    * Select Reference Document Number from RBKP table
    SELECT BELNR XBLNR
           FROM RBKP
           INTO TABLE GT_RBKP
           WHERE BELNR = objky . " .WA1_OBJKY .
    IF SY-SUBRC EQ 0 .
      LOOP AT GT_RBKP INTO WA_RBKP.
        WA1_OBJECT_ID = WA_RBKP-XBLNR .
        CONCATENATE WA1_OBJECT_ID '%' INTO WA1_OBJECT_ID .
        WA_SAP_OBJECT = WA_RBKP-BELNR .
        SELECT OBJECT_ID
               ARC_DOC_ID
               FROM TOA01
               INTO TABLE GT_ARC_DOC_ID
               WHERE  OBJECT_ID LIKE WA1_OBJECT_ID.
        IF SY-SUBRC EQ 0 .
          READ TABLE GT_ARC_DOC_ID INTO WA_ARC_DOC_ID INDEX 1.
          ARC_DOC_ID = WA_ARC_DOC_ID-ARC_DOC_ID.
          WA_SAP_OBJECT = WA_ARC_DOC_ID-OBJECT_ID.
        ENDIF.
    CALL Function Module:Link table operations
        CALL FUNCTION 'ARCHIV_CONNECTION_INSERT'
               EXPORTING
                ARCHIV_ID                   = 'Z0'
                 ARC_DOC_ID                 = ARC_DOC_ID
               AR_DATE                     = SY-DATUM
                 AR_OBJECT                  = 'MMILOGINV'
            DEL_DATE                   = ' '
                MANDANT                     = SY-MANDT
                 OBJECT_ID                  = WA_SAP_OBJECT
                 SAP_OBJECT                 = 'BUS2081'
                DOC_TYPE                    = 'PDF'
            BARCODE                    = ' '
             EXCEPTIONS
             ERROR_CONNECTIONTABLE      = 1
             OTHERS                     = 2
        IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
        CLEAR: WA_RBKP.
      ENDLOOP.
    ENDIF.
    ENDFORM.
    Edited by: Thomas Zloch on Oct 26, 2011 10:52 AM

    ok, if you set for your output type NAST-VSZTP=3 you can add code in your print program to display popup window in which
    user specify own path for storing PDF...
    but if output type will be created in background ( VSZTP ne 3) then
    you must save PDF in server path...and user may download it by
    cg3y...
    regards, darek

  • Posting from FICA to another instance

    Is it at all possible to post directly from SAP FICA or CD in one instance to SAP FICO in another instance or should the initial posting be done in the SAP FICA instance and the transfer it via I-docs or something similar to FICO in the other instance?
    Rgrds,
    Arnoud

    Arnoud:
    The second approach is the correct one - you can make use of idocs to communicate GL postings form one system to the consolidated system.  There must be GL in the same system as the FICA so that reconciliation can be done.  SAP has many clients who use distributed landscape with GL idocs.
    regards,
    bill.

  • IDOC not displayed in billing document

    Hi Experts,
    I have a issue about the outbound idoc's generated from two different billing document.
    I can see the idoc's from these documents though the path Goto>header>Output ---> Processing log.
    But if i check the services of object button for one billing document, i can see the same idoc.but for the other document, its not displaying idoc number....in the relationships button..
    What could be the cause?
    What is the difference between these two documents ?

    Dear Mr. Kapil and Madhurao,
    Thank you for your help and quick response.
    I followed your instaructions and found that the option "Relevant for Order-related billing - - Status acc. to order Qty" "B" is already maintained.
    Also, i have to mention that this is not the first time we use this service material in our orders and we weren't facing any problem. This is the first time we face such issue.
    so please let me know if there's any other option to check.
    Thank you

  • Credit Memo request with reference to Billing Document number via IDoc

    Hi,
    I want to create credit memo request with reference to billing document number via IDocs.
    I have tried through ORDERS05, but when I process I saw that it is only processing with reference to contract  number or quotation.
    So is any other way of creating credit memo request creation with reference to Billing document number via IDocs?
    Thank you in advance.
    Regards,
    Santhi

    Please Help... it is Urgent...  Thank you

  • Creation of a billing document from an idoc

    Dear all,
    I'd want to find a soulution for the following scenario:
    The need is to create automatically an accompany invoice when a good issue is posted.
    I think that a possible solution should be:
    -an output type linked to the delivery document (generated when the good issue is posted)
    -the idoc generate the billing document
    Is this scenario possible?If yes which is the kind of idoc (INVOIC02?) and the parameters to be used in order to create the billing documents? (Ale settings, for example BD64 ecc..) 
    Best Regards
    Many Thanks
    Angelo Gaiatto

    Hi,
    There is a simple solution provided by SAP to trigger the BILLING DOCUMENTS for Deliveries
    This is a standard process
    Setup a Job in SM36 for the program SDBILLDL and it will pick all the delivery document which are open on that particular Billing date
    and process the Billing documents
    Alternatively you can also create the IDOC to trigger the BILLING DOCUMENTS
    For which you need to setup the PARTNER PROFILES, MESSAGE TYPES, PORT, RFC DESTINATION, SEGMENT CREATION,
    But i would suggest you to go with the standard program to create the Billing documents
    regards,
    santosh

  • Return order with reference to the billing document created via IDOC.

    Dear Colleagues,
    I’m struggling to understand and confirm whether standard functionality of ORDERS05 idoc allows creating a return order with reference to existing billing document?
    I have tried using standard segment E1EDK02 and E1EDP02 with qualifiers 009,010,011,087 but unfortunately idol is not creating a return order with reference and ignoring this segment.
    Have any one came across similar problem? If yes then will be grateful for sharing his experience.
    Best regards,
    AL

    Dear Friend
    Welcome to SDN
    Return order is itself a challenge to SAP standard settings
    There are some scenarios
    1. Return order qty should not be increasesd say Billed qty of material X is 20 units
    While returning Material X should be a maximum of 20 units
    If made 21 it should throw error T code OVAH message class V4 message no 299 convert from warning to error thro customization
    2.Return order should be created only once referencing billing doc
    To control that T code SE91 message class V1 message no 499 convert from warning to error thro ABAP help
    3 Your issue is same like case 1 but the material X is entered as second line item in the return order with some qty
    This case system is not throwing even a warning
    Yes correct
    This is to be handled with userexit
    Discuss the same with ABAPer
    Check these threads on return issues which is of different scenario than of yours
    Forum post in ERP - Sales and Distribution (SD) General: Order Qty.
    Order Qty.
    Forum post in ERP - Sales and Distribution (SD) General: Return order
    Return order
    Regards
    Raja

Maybe you are looking for