IDoc details

Hi all,
     I am new to Idoc scenraio’s. I need to work with it.   Can any body tell what is use of the (Logical system, logical system client, Partner profile outbound inbound, port creation, and also tell how they are inter linked among them self.

Hope this will help.
Partner profile :: Every sender-receiver relationship needs a profile defined. This one determines
The processing code
The processing times and conditions
In the case of outbound IDoc 1. The media port used to send the IDoc and 2. Triggers used to send the IDoc
Partner Type :: The IDoc partners are classified in logical groups. Such as : LS, KU, LI.
LS - Logical Systems : It is meant to be a different computer and was primarily introduced for use with the ALE functionality.
KU - Customer : The partner type customer is used in classical EDI transmission to designate a partner, that requires a service from your company or is in the role of a debtor with respect to your company, e.g. the payer, sold-to-party, ship-to-party.
LI - Supplier : The partner type supplier is used in classical EDI transmission to designate a partner, that delivers a service to your company.
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
• Create a Customer Distribution Model (CDM);
• Add appropriate message types and filters to the CDM;
• Generate outbound partner profiles;
• Distribute the CDM to the receiving systems; and
• Generate inbound partner profiles on each of the clients.
Regards,
Vishal
**Reward if helpful

Similar Messages

  • Table for Idoc details including messageID

    Hello All.
    Is there any table in ECC end , where we can get inbound iDoc details including message ID (which is same as that of Message ID of XI sender system )
    I need to find this MessageID information for thousands of IDoc.
    Normally we need to open each idoc control structure's Detail tab to find this.
    Thanks,
    Shiv

    Hello Avinash,
    I already seen in tables  EDIDC and EDIDS but not able to find the message ID details of sender system (XI system ) .
    Thanks,
    XI team

  • Getting IDOC details-function module

    Hi ,
    Is there any function module(importing parameter shld be Idoc No) available to get the IDOC details - Data records
    There is a urgent requirement
    1 To get the details of the idoc-data records
    2 To change the data
    Thanks in advance
    Regards,
    Sachin

    Hi Sachin,
    The concept that is generally followed is to create a new IDoc and process it instead of amending the old one. There are various reasons for this and one of the reason is if you have processed it , and if it's outbound then informaiton would have already been sent.
    If you are somehow able to change it then also you need to send it again to theother system. And if that is to be done then you might as well create a new one
    Hope this clarifies the issue.
    Regards
    Nishant

  • Download idoc details to a file

    Hi,
    Is there any way i can downlaod an IDOC details from we05 or any other transaction into a file on my dektop. The file cna be  a excel or notepad etc file
    Regards,

    Hi,
    follow the steps:
    Input t-code IDOC
    In selection screen, select 'Analyse IDOC field values
    Press F8
    Input your IDOC number
    Check mark on 'Also evaluate empty fields
    Click on 'Output in internal form' : this is very much important thing
    The execute
    You will see all the data
    Then go to 'List'>Save/send option from where you can achieve your purpose.
    Thanks!

  • How to create Inbound Delivery using SHPMNT03 Idoc details...

    Hi,
         I need to create <b><b>Inbound delivery</b> using idoc SHPMNT03</b> details. I am getting all the data required to create Inbound delivery is from this idoc. for that I need to create a custom function module.
    I tried with FM  IDOC_INPUT_DESADV1. But it is for only if you use DELVRY03.
    I haven't (yet) found a way to create automatically an inbound delivery when you post the goods issue from the outbound delivery.
    Does anyone experienced the use of inbound deliveries with STO and what are your recommendation?
    Thanks a lot,
    Ranjith.

    Hi there,
    Please have a look at the following link.
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/dc/6b828943d711d1893e0000e8323c4f/frameset.htm
    Hope this helps,
    Kind Regards,
    Matthew

  • Service Contract (VA41/VA42) Outbound IDOC Details

    Hi ,
    I have to send the changes in the Service contract from SAP to Third party system when ever contract is changed.I am able to send the IDOC with the output type KO00 and process code SD10 but it doesn't contain any contract details like start date and end date i.e the data from VEDA table.
    Please let me know is there any standard Process code available for this, otherwise i have to extend the standard ORDERS with the contract related fields.
    Please suggest me regarding the above.
    Thanks & Regards,
    Rajesh.

    What are the details of the contract you need? Some specific detail?
    Maybe we should develop an IDOC 'Z' depending on the information you need ..

  • IDoc Detailed documentation

    Dear Friends,
    I need the detailed documentation on IDocs and ALE pertaining to SD module.

    Hi
    http://www.sapmaterial.com/idoc_sample.html
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0087780d-81b0-2a10-eb82-86e1062f1a2d

  • FIDCCP02 IDOCs : Details for Customer Invoice Clearing

    We are planning on using FIDCCP02 IDOCs to post customer invoice clearing.
    The IDOC gets created however when we check the IDOC status, it states that "Document does not contain any valid line items
    Message no. F5079"
    Can someone please let me know which segments and what fields we need to populate specifically for Invoice Clearing?
    We are populating the following segments:
    E1FIKPF
    -- E1FISEG
        ---E1FISE2
        ---E1FINBU
    --E1FISEC
    --E1FISET
    EDIDD     Data Records     
    SEGNUM     Segment Number                          000001
    SEGNAM     Segment Name                          E1FIKPF
    BUKRS     Name of global company code     ABCD
    BELNR     Accounting Document Number     3510452953
    GJAHR     Fiscal Year                                                2011
    BLART     Document Type                           AB
    BLDAT     Document Date in Document     20110329
    BUDAT     Posting Date in the Document     20110329
    MONAT     Fiscal Period     3
    WWERT     Translation Date                          20110329
    USNAM     User Name                                                TEST
    TCODE     Transaction Code     FB05
    WAERS     Currency Key     USD
    GLVOR     Business Transaction     RFBU
    AWTYP     Reference Transaction     BKPFF
    SEGNUM     Segment Number     000002
    SEGNAM     Segment Name     E1FISEG
    BUZEI     Number of Line Item Within Acc     001
    BSCHL     Posting Key     40
    KOART     Account Type     S  : G/L accounts
    SHKZG     Debit/Credit Indicator     S  : Debit
    DMBTR     Amount in Local Currency     42.79
    HKONT     General Ledger Account     0000113434
    SEGNUM     Segment Number     000003
    SEGNAM     Segment Name     E1FISE2
    SEGNUM     Segment Number     000004
    SEGNAM     Segment Name     E1FINBU
    KUNNR     Customer Number 1     0060000006
    PYCUR     Currency for Automatic Payment     USD
    PYAMT     Amount in Payment Currency     42.79
    SEGNUM     Segment Number                          000005
    SEGNAM     Segment Name                          E1FISEC
    BUZEI     Number of Line Item Within Acc     001
    SEGNUM     Segment Number                          000006
    SEGNAM     Segment Name                          E1FISET
    EDIDS     Status Records     
    EDIDS     Status Record Number     1
    Thanks

    We are planning on using FIDCCP02 IDOCs to post customer invoice clearing.
    The IDOC gets created however when we check the IDOC status, it states that "Document does not contain any valid line items
    Message no. F5079"
    Can someone please let me know which segments and what fields we need to populate specifically for Invoice Clearing?
    We are populating the following segments:
    E1FIKPF
    -- E1FISEG
        ---E1FISE2
        ---E1FINBU
    --E1FISEC
    --E1FISET
    EDIDD     Data Records     
    SEGNUM     Segment Number                          000001
    SEGNAM     Segment Name                          E1FIKPF
    BUKRS     Name of global company code     ABCD
    BELNR     Accounting Document Number     3510452953
    GJAHR     Fiscal Year                                                2011
    BLART     Document Type                           AB
    BLDAT     Document Date in Document     20110329
    BUDAT     Posting Date in the Document     20110329
    MONAT     Fiscal Period     3
    WWERT     Translation Date                          20110329
    USNAM     User Name                                                TEST
    TCODE     Transaction Code     FB05
    WAERS     Currency Key     USD
    GLVOR     Business Transaction     RFBU
    AWTYP     Reference Transaction     BKPFF
    SEGNUM     Segment Number     000002
    SEGNAM     Segment Name     E1FISEG
    BUZEI     Number of Line Item Within Acc     001
    BSCHL     Posting Key     40
    KOART     Account Type     S  : G/L accounts
    SHKZG     Debit/Credit Indicator     S  : Debit
    DMBTR     Amount in Local Currency     42.79
    HKONT     General Ledger Account     0000113434
    SEGNUM     Segment Number     000003
    SEGNAM     Segment Name     E1FISE2
    SEGNUM     Segment Number     000004
    SEGNAM     Segment Name     E1FINBU
    KUNNR     Customer Number 1     0060000006
    PYCUR     Currency for Automatic Payment     USD
    PYAMT     Amount in Payment Currency     42.79
    SEGNUM     Segment Number                          000005
    SEGNAM     Segment Name                          E1FISEC
    BUZEI     Number of Line Item Within Acc     001
    SEGNUM     Segment Number                          000006
    SEGNAM     Segment Name                          E1FISET
    EDIDS     Status Records     
    EDIDS     Status Record Number     1
    Thanks

  • Inbound delivery creation using shipment Idoc details

    Hi,
       My requirement is that I need to create inbound delivery using SHPMNT05 idoc sending from a different plant.
    Below are the fields I am getting from the SHPMNT05 Idoc. So I need to create  Inbound delivery in Receiving plant.
    SAP - Field     IDoc Segment- Position - Field Name
    LIKP-LFART     E1EDL21 – 001 – LFART
    LIKP-LIFEX     E1EDT01 – 001 – VBELN
    LIKP-LIFNR     E1EDT44 – 009 – LIFNR
    LIKP-MBDAT     E1EDL24 – 039 = ABRDT
    LIPS-LFIMG     E1EDL24 – 013 – LFIMG
    LIPS-MATNR     E1EDL24 – 002 – MATNR
    LIPS-VGPOS     E1EDL41 – 006 – POSEX
    LIPS-PSTYV     E1EDL26 – 001 – PSTYV
    LIPS-VGBEL     E1EDL41 – 002 – BSTNR
    LIPS-VRKME     E1EDL24 – 014 – VRKME
    VEKP-EXIDV     E1EDL37 – 001 – EXIDV
    VEKP-VHILM     E1EDL37 – 017 – VHILM
    VEPO-MATNR     E1EDL44 – 007 – MATNR
    VEPO-POSNR     E1EDL44 – 003 - POSNR
    VEPO-VBELN     E1EDL44 – 002 - VBELN
    VEPO-VELIN     E1EDL44 – 001 – VELIN
    VEPO-VEMEH     E1EDL44 – 006 – VEMEH
    VEPO-VEMNG     E1EDL44 – 005 – VEMNG
    Could you please help me to find some workaround to solve this ?
    Thanks in advance.
    Regards.
    Ranjith

    Hi Ranjith,
    I guess there is a BAPI " /SPE/INB_DELIVERY_REPLACE " which can be used to create an inbound delivery.
    Documentation-
    FU /SPE/INB_DELIVERY_REPLACE
    Short Text
    Create inbound delivery
    Functionality
    You can use this method to distribute inbound deliveries from an ERP system to a WM system.
    The following parameters are required:
    HEADER_DATA Inbound delivery header data
    SENDER_SYSTEM System of the sender
    HEADER_PARTNER Header data of the partners
    HEADER_DEADLINES Header data of the dates
    ITEM_DATA Item data of the inbound delivery
    ITEM_ORG Organisation data of the inbound delivery
    Notes
    The required parameters have the following required fields:
    Import parameter HEADER_DATA
    INB_DELVRY_NO
    DLV_TYPE
    Import parameter SENDER_SYSTEM
    SENDERSYSTEM
    Table parameter HEADER_PARTNER
    PARTN_ROLE = 'LF'   Vendor is required partner
    PARTNER_NO
    Table parameter HEADER_DEADLINES
    TIMETYPE = 'WSHDRLFDAT' Delivery date
    Table parameter ITEM_DATA
    INB_DELVRY_NO
    ITM_NUMBER
    MATERIAL
    DLV_QTY
    SALES_UNIT_ISO oder SALES_UNIT
    Table parameter ITEM_DATA_ORG
    PLANT
    Further information
    HEADER_PARTNER
    Since the partners in the delivery are not managed on an item basis, the ITM_NUMBER field in the BAPIDLVPARTNER segment is left blank and not analyzed.
    HANDLING_UNIT_ITEM
    If the BAPI is used as an external interface for an external system, the packing hierarchy should be described as usual by using external identification numbers for shipping materials (HDL_UNIT_EXID_INTO/HDL_UNIT_EXID).
    Parameters
    HEADER_DATA
    SENDER_SYSTEM
    TECHN_CONTROL
    HEADER_DATA_SPL
    HEADER_CONTROL_SPL
    HEADER_PARTNER
    HEADER_PARTNER_ADDR
    HEADER_DEADLINES
    ITEM_DATA
    ITEM_ORG
    ITEM_STOCK_TRANS
    ITEM_CODING_BLOCK
    ITEM_REF_PURCHASE_ORDER
    ITEM_SERIAL_NO
    ITEM_DATA_SPL
    TEXT_HEADER
    TEXT_LINES
    HANDLING_UNIT_HEADER
    HANDLING_UNIT_ITEM
    HANDLING_UNIT_SERNO
    HANDLING_UNIT_ITEM_SPL
    HANDLING_UNIT_HEADER_CROSS
    HANDLING_UNIT_IDENTIFIERS
    EXTENSION1
    EXTENSION2
    RETURN
    TOKENREFERENCE
    Exceptions
    Function Group
    /SPE/INB_DELIVERY
    Check if this helps.
    Reward helpful answers.
    Regards
    Parag

  • Automated error email notification when outbound IDOC fails

    Hi,
    The requirement is that whenever the outbound IDOC of message type PAYEXT, basic type PEXR2002, fails, then email has to be trigerred to a group id.
    I had suggested to write a report program that runs as a job. If the IDOC goes to error status then mail will be sent from this report. Client prefers it to be done through workflow.
    There is a standard process code for outbound IDOC failure handling EDIO (we40). standard task 7989 has been assigned to this process code. I dont want to modify this standard task as I am not sure of impact.
    Terminating event for this task is 'ERRORPROCESSCOMPLETD'.
    I have developed the workflow that has trigerring event 'ERRORPROCESSCOMPLETD' and bound with the IDOC number. This will send mail to the group id with the IDOC details
    Now issue is that, I am not sure if standard process EDIO will be trigerred automatically, or should we configure anywhere. Since this is standard outbound IDOC, I am not able to add the process code in partner profile.
    Please give your inputs or any other alternate solution to send mail through workflow when  outbound IDOC fails.
    Thanks in advance.

    Hi,
    I guess in your outbound partner profile for PAYEXT. you need to add process code  EDIO in message control TAb. WHich will cause to trigger the workflow which will send the notification.

  • How can we send Error Idocs via mail

    Hi,
    I have read read through forums and  understood that it can be achieved either through workflow or through report using table edidd & edids.
    If workflow option is used , does the mail trigger for every error idoc ? How can we send daily error report to user say by EOD containing all error idocs using all possible options.
    Regards,
    Rachel

    Rachel,
    I dont think so any direct Report will be available just to get Error IDOCs details. Although you can create a simple report to read the tables. An example is in below link.
    http://wiki.scn.sap.com/wiki/display/Snippets/Custom+report+for+IDOC+Monitoring
    Also, you can create a Query of EDIDC and EDIDS tables to obatin relevant information.
    Thanks,
    Ravi

  • Segment management in ORDERS05 IDOC.

    Hi there.
    I have two questions, one is very focused on text management in ORDERS05, the other one is more generally speaking.
    1 - Text management in ORDERS05 IDoc:
    I have texts in my purchase order that I fill in, and then generate my IDoc. When looking at IDoc detail through WE05 or WE02, my texts are not visible neither in E1EDKT1 nor E1EDPT1 segments. Basically, those segments are not even created in my IDoc. Why? Anything to do in PO and/or ALE customizing?
    2 - More general:
    I need to have, in my E1EDS01 segment, the total quantity I order in my PO. So, I need a segment with qualifier '004' in SUMID, then my quantities. Currently, I only have SUMID='002' and my total value amount. How can I define (or it is defined by the system) the type of information I have in my segments, or segments themselves?
    Please tell me if not clear at all.
    Thanks for your answers.
    Chris.

    Thanks Dani.
    I checked the T166A table and found that the following entries are missing for my cases: EKPO and EKKO for my ZNB PO type.
    Shall I just put an entry for those two things in that table and this will allow me to get my texts in my ORDERS05 IDoc?
    For point 2, as I am not an ABAP developper, I do not understand what to do. I can deal with customizing, but not with ABAP programming on that subject.
    Thanks anyway at least for the first part of the answer.

  • IDOC creation after the creation of a purchase order

    Hi everybody,
                I want some configuration details regardign IDOC creation. The requirement is, once i create a purchase order in one system, the details should automatciaclly transfer to other system through IDOC. could any one suggest any document or detailed procedure to accomplish the task. Thanks in advance,
             Santosh.

    hi santosh kumar,
    Creating an IDoc Segment WE31:
    The segment defines the structure of the records in an IDoc. They are defined with transaction WE31.
    We will define a structure to send a text from the text database.
    Transaction WE31 calls the IDoc segment editor. The editor defines the fields of a
    single segment structure. The thus defined IDoc segment is then created as a data
    dictionary structure. You can view the created structure with SE11 and use it in an
    ABAP as any TABLES declaration.
    To demonstrate the use of the IDoc segment editor we will set up an example, which
    allows you to send a single text from the text pool (tables STXH and STXL) as an
    IDoc. These are the texts that you can see with SO10 or edit from within many
    applications.
    We will show the steps to define an IDoc segment YAXX_THEAD with the DDic
    structure of THEAD.
    To facilitate our work, we will use the "copy-from-template-tool", which reads the
    definition of a DDIC structure and inserts the field and the matching definitions as
    rows in the IDoc editor. You could, of course, define the structure completely
    manually, but using the template makes it easier.
    The tool in release 4.0b lets you use both DDIC structures or another IDoc segment
    definition as a template.
    The thus created structure can be edited any time. When saving, it will create a data
    dictionary structure based on the definition in WE31. The DDIC structure will retain
    the same name. You can view the structure as a table definition with SE11 and use it
    in an ABAP the same way.
    Defining the Message Type (EDMSG)
    The message type defines the context under which an IDoc is transferred to its destination. It allows for using the same IDoc file format for several different applications.
    Imagine the situation of sending a purchase order to a supplier. When the IDoc with
    the purchase order reaches the supplier, it will be interpreted as a sales order
    received from a customer, namely you.
    Simultaneously you want to send the IDoc data to the supplier's warehouse to inform
    it that a purchase order has been issued and is on the way.
    Both IDoc receivers will receive the same IDoc format; however, the IDoc will be
    tagged with a different message type. While the IDoc to the supplier will be flagged
    as a purchase order (in SAP R/3 standard: message type = ORDERS), the same IDoc
    sent to the warehouse should be flagged differently, so that the warehouse can
    recognize the order as a mere informational copy and process it differently than a
    true purchase order.
    The message type together with the IDoc type determine the processing function.
    The message types are stored in table EDMSG.
    Defining the message type can be done from the transaction WEDI
    EDMSG: Defining the message type (1)
    The entry is only a base entry which tells the system that the message type is
    allowed. Other transactions will use that table as a check table to validate the entry.
    IT is as shown .
    EDMSG: Defining the message type (1):
    The entry is only a base entry which tells the system that the message type is
    allowed. Other transactions will use that table as a check table to validate the entry.
    Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.
    Requirement:
    Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.
    Processing:
    The report selects, 'ORDERS' IDoc numbers & status, generated between given time range, from table EDIDC. Further, it calls Function Module 'IDOC_READ_COMPLETELY' to get the IDoc details. Then required information is extracted by reading relevant field data of IDoc segments.
    sampl code:
    REPORT  Z_EDI_FILE_LOAD_STATUS_REPORT           .
    Staus Report for Inbound IDOCs ( Sales Orders )
    Program        : Z_EDI_FILE_LOAD_STATUS_REPORT
    Presented By   : www.rmtiwari.com
    TABLES : EDIDC.
    ALV stuff
    TYPE-POOLS: SLIS.
    DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
          GS_LAYOUT   TYPE SLIS_LAYOUT_ALV,
          GT_SORT     TYPE SLIS_T_SORTINFO_ALV,
          GT_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
    DATA : BEGIN OF T_REPORT OCCURS 0,
             IDOC_NO       TYPE EDI_DOCNUM,
             IDOC_DATE     TYPE SY-DATUM,
             IDOC_TIME     TYPE SY-UZEIT,
             SORDER_NO     TYPE VBELN,
             STP_NO        TYPE KNA1-KUNNR,
             STP_NAME(35)  TYPE C,
             STP_PHONE(12) TYPE C,
             PO_NO(15)     TYPE C,
             STATUS        TYPE C,
             S_TEXT(70)    TYPE C,
             ERROR(70)     TYPE C,
           END OF T_REPORT.
    --PARAMETER--
    selection-screen begin of block date with frame title TEXT-S01.
    select-options: UDATE for  EDIDC-UPDDAT
                          default SY-datum obligatory,    "Changed On
                    UTIME for  EDIDC-UPDTIM .             "Changed Time
    selection-screen end   of block date.
    INITIALIZATION.
    START-OF-SELECTION.
    PERFORM SHOW_STATUS_REPORT.
    *&      Form  alv_grid
          text
    -->   p1        text
    < --  p2        text
    FORM ALV_GRID.
      IF GT_FIELDCAT[] IS INITIAL.
        PERFORM FIELDCAT_INIT.
        PERFORM LAYOUT_INIT.
        PERFORM SORT_INIT.
      ENDIF.
      PERFORM GRID_DISPLAY.
    ENDFORM.                    "alv_grid
    *&      Form  layout_init
    FORM LAYOUT_INIT.
      GS_LAYOUT-ZEBRA             = 'X'.
      GS_LAYOUT-CELL_MERGE        = 'X'.
      GS_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
      GS_LAYOUT-NO_VLINE          = ' '.
      GS_LAYOUT-TOTALS_BEFORE_ITEMS = ' '.
    ENDFORM.                    " layout_init
    *&      Form  fieldcat_init
    FORM FIELDCAT_INIT.
      DATA: LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
       CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'IDOC_NO'.
      LS_FIELDCAT-KEY          = 'X'.
      LS_FIELDCAT-REPTEXT_DDIC = 'IDOC'.
      LS_FIELDCAT-OUTPUTLEN    = 10.
    Fix for ALV print bug, which puts 'N/A' over last digit
    Set inttype to 'N' to stop corruption of printed ALV cell.
      LS_FIELDCAT-INTTYPE = 'N'.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'IDOC_DATE'.
      LS_FIELDCAT-REPTEXT_DDIC = 'Creation Date'.
      LS_FIELDCAT-OUTPUTLEN    = 10.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'IDOC_TIME'.
      LS_FIELDCAT-REPTEXT_DDIC = 'Creation Time'.
      LS_FIELDCAT-OUTPUTLEN    = 8.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'STATUS'.
      LS_FIELDCAT-REPTEXT_DDIC = 'St'.
      LS_FIELDCAT-OUTPUTLEN    = 2.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'ERROR'.
      LS_FIELDCAT-REPTEXT_DDIC = 'Message'.
      LS_FIELDCAT-OUTPUTLEN    = 70.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'STP_NO'.
      LS_FIELDCAT-REPTEXT_DDIC = 'S.T.Party No'.
      LS_FIELDCAT-OUTPUTLEN    = 10.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'STP_NAME'.
      LS_FIELDCAT-REPTEXT_DDIC = 'Sold to Party Name'.
      LS_FIELDCAT-OUTPUTLEN    = 35.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'PO_NO'.
      LS_FIELDCAT-REPTEXT_DDIC = 'Purch Order'.
      LS_FIELDCAT-OUTPUTLEN    = 15.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
      CLEAR LS_FIELDCAT.
      LS_FIELDCAT-FIELDNAME    = 'STP_PHONE'.
      LS_FIELDCAT-REPTEXT_DDIC = 'S.T.Party Phone'.
      LS_FIELDCAT-OUTPUTLEN    = 15.
      APPEND LS_FIELDCAT TO GT_FIELDCAT.
    ENDFORM.                    "fieldcat_init
    *&      Form  sort_init
    FORM SORT_INIT.
      DATA: LS_SORT TYPE SLIS_SORTINFO_ALV.
      CLEAR LS_SORT.
      LS_SORT-FIELDNAME = 'IDOC_DATE'.
      LS_SORT-SPOS      = 1.
      LS_SORT-UP        = 'X'.
      APPEND LS_SORT TO GT_SORT.
      CLEAR LS_SORT.
      LS_SORT-FIELDNAME = 'IDOC_TIME'.
      LS_SORT-SPOS      = 2.
      LS_SORT-UP        = 'X'.
      APPEND LS_SORT TO GT_SORT.
      CLEAR LS_SORT.
      LS_SORT-FIELDNAME = 'STATUS'.
      LS_SORT-SPOS      = 3.
      LS_SORT-UP        = 'X'.
      APPEND LS_SORT TO GT_SORT.
      CLEAR LS_SORT.
      LS_SORT-FIELDNAME = 'IDOC_NO'.
      LS_SORT-SPOS      = 4.
      LS_SORT-UP        = 'X'.
      APPEND LS_SORT TO GT_SORT.
    ENDFORM.                    "sort_init
    *&      Form  grid_display
    FORM GRID_DISPLAY.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          IS_LAYOUT     = GS_LAYOUT
          IT_FIELDCAT   = GT_FIELDCAT
          IT_SORT       = GT_SORT
          i_callback_program      = SY-REPID
          I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
          I_DEFAULT     = ' '
          I_SAVE        = 'X'
        TABLES
          T_OUTTAB      = T_REPORT
        EXCEPTIONS
          PROGRAM_ERROR = 1
          OTHERS        = 2.
    ENDFORM.                    "grid_display
    *&      Form  COMMENT_BUILD
          Processing of listheader
    FORM COMMENT_BUILD USING P_FK_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
      DATA: LS_LINE TYPE SLIS_LISTHEADER.
      REFRESH P_FK_LIST_TOP_OF_PAGE.
    List Heading : Typ H
      CLEAR LS_LINE.
      LS_LINE-TYP  = 'H'.
      LS_LINE-INFO  = 'Sales Order Interface: Z_EDI_FILE_LOAD'.
      APPEND LS_LINE TO P_FK_LIST_TOP_OF_PAGE.
    List : Typ S
      clear LS_LINE.
      LS_LINE-typ  = 'S'.
      LS_LINE-key  = 'Date Range:'.
      LS_LINE-info  = UDATE-low.
      if not UDATE-high is initial.
        write ' To ' to  LS_LINE-info+30.
        LS_LINE-info+36 = UDATE-high.
      endif.
      APPEND LS_LINE TO P_FK_LIST_TOP_OF_PAGE.
    ENDFORM.                               " COMMENT_BUILD
          FORM TOP_OF_PAGE                                              *
          Ereigniss TOP_OF_PAGE                                       *
          event     TOP_OF_PAGE
    FORM TOP_OF_PAGE.
      PERFORM COMMENT_BUILD  USING gt_LIST_TOP_OF_PAGE[].
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
        EXPORTING
          IT_LIST_COMMENTARY = GT_LIST_TOP_OF_PAGE.
    ENDFORM.                    "TOP_OF_PAGE
    *&      Form  show_status_report
    FORM SHOW_STATUS_REPORT .
    Report to show status.
      DATA: BEGIN OF T_TEDS2 OCCURS 0.
              INCLUDE STRUCTURE TEDS2.
      DATA: END OF T_TEDS2.
      DATA: BEGIN OF T_IDOC_CONTROL_TMP OCCURS 0.
              INCLUDE STRUCTURE EDIDC.
      DATA: END OF T_IDOC_CONTROL_TMP.
      CONSTANTS: C_STATUS_IN_IDOC_POSTED       LIKE EDIDC-STATUS VALUE '53'.
      DATA : T_EDIDS TYPE STANDARD TABLE OF EDIDS WITH HEADER LINE.
      DATA : T_EDIDD TYPE STANDARD TABLE OF EDIDD WITH HEADER LINE.
      DATA : GV_PARTNER_SEG TYPE E1EDKA1,
             GV_PO_REF_SEG  TYPE E2EDK02.
    Get text for status values
      SELECT * FROM TEDS2 INTO TABLE T_TEDS2 WHERE LANGUA = SY-LANGU.
    Read the IDoc's status after processing
      SELECT * FROM EDIDC
        INTO TABLE T_IDOC_CONTROL_TMP
       WHERE UPDDAT IN UDATE
         AND UPDTIM IN UTIME
         AND MESTYP = 'ORDERS'.
      LOOP AT T_IDOC_CONTROL_TMP.
      IDoc has been processed, since control record changed.
        READ TABLE T_TEDS2 WITH KEY STATUS = T_IDOC_CONTROL_TMP-STATUS.
        T_REPORT-IDOC_NO = T_IDOC_CONTROL_TMP-DOCNUM.
        T_REPORT-IDOC_DATE = T_IDOC_CONTROL_TMP-CREDAT.
        T_REPORT-IDOC_TIME = T_IDOC_CONTROL_TMP-CRETIM.
        T_REPORT-S_TEXT = T_TEDS2-DESCRP.
        IF T_IDOC_CONTROL_TMP-STATUS = C_STATUS_IN_IDOC_POSTED.
        ok status
          T_REPORT-STATUS = 'S'.
        ELSE.
        error status
          T_REPORT-STATUS = 'E'.
        ENDIF.
        Get IDoc details.
        CALL FUNCTION 'IDOC_READ_COMPLETELY'
          EXPORTING
            DOCUMENT_NUMBER         = T_REPORT-IDOC_NO
          TABLES
            INT_EDIDS               = T_EDIDS
            INT_EDIDD               = T_EDIDD
          EXCEPTIONS
            DOCUMENT_NOT_EXIST      = 1
            DOCUMENT_NUMBER_INVALID = 2
            OTHERS                  = 3.
      Get Error status
        READ TABLE T_EDIDS WITH KEY STATUS = T_IDOC_CONTROL_TMP-STATUS.
        IF SY-SUBRC EQ 0.
          REPLACE FIRST OCCURRENCE OF '&1' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA1.
          REPLACE FIRST OCCURRENCE OF '&2' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA2.
          REPLACE FIRST OCCURRENCE OF '&3' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA3.
          REPLACE FIRST OCCURRENCE OF '&4' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA4.
          REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA1.
          REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA2.
          REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA3.
          REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
                                WITH T_EDIDS-STAPA4.
          T_REPORT-ERROR = T_EDIDS-STATXT.
        ENDIF.
        LOOP AT T_EDIDD.
          CASE T_EDIDD-SEGNAM.
            WHEN 'E1EDKA1'.
              GV_PARTNER_SEG = T_EDIDD-SDATA.
              CLEAR : T_REPORT-STP_NAME.
              CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  INPUT  = GV_PARTNER_SEG-PARTN
                IMPORTING
                  OUTPUT = T_REPORT-STP_NO.
              SELECT SINGLE NAME1 TELF1
                INTO (T_REPORT-STP_NAME,T_REPORT-STP_PHONE)
                FROM KNA1
               WHERE KUNNR = T_REPORT-STP_NO.
            WHEN 'E1EDK02'.
              GV_PO_REF_SEG = T_EDIDD-SDATA.
              T_REPORT-PO_NO = GV_PO_REF_SEG-BELNR.
          ENDCASE.
        ENDLOOP.
        APPEND T_REPORT.
      ENDLOOP .
      SORT T_REPORT BY STATUS IDOC_NO.
    Show Report
      PERFORM ALV_GRID.
    ENDFORM.                    " show_status_report
    thanks
    karthik
    reward me points if usefull.

  • Auto SO from PO- ALE IDoc

    Hi Friends,
    Someone provide me basic process flow and steps to automate creation of Sales Order in another Company Code when a Purchase Order is created in a separate Ccd with the help of IDocs. Eg: (PO saved in CCd-1100 triggering a SO in CCd-2200)
    I know that there are two separate settings for this,
    1. PO Message settings for ALE in NACE
    2. Configurations in SALE for IDoc
    But I want to have a clearer idea as to how to acheive this.
    Any inputs highly apprecieated!!
    Thanks in adv
    Suraj

    To create SO from the PO, you need to set up partner profile, process code. Etc.
    First from PO the outbound IDOC you can use the below FM and basic type.
    The SAP std basic type : ORDERS05
    For the function module: IDOC_OUTPUT_ORDERS.
    Table: EDP12- Partner Profile: Outbound with Message Control
    T code: WE41 to set up the out bound process code
    To create sales order inbound IDOC details.
    The SAP Std basic : ORDERS05
    Function module: IDOC_INPUT_ORDERS
    T code: WE42 to set up inbound process code
    Thanks
    JRP

  • Ship to party not populating in segment in whsord idoc

    HI,
    we are creating two delivery with ship to party as 52004 and 56003 (two different sales orders with differnt sold to ). the deliveries are trigerring outbound whsord idoc. The issue is in the segment E1ADRM1 segment for WE qualifier , in the field, " Partner_id", the ship to party 52004 and 56003 is not populated. Rather a constant value 32500000789 is populated in "partner_id " field in both deliveries
    Our Abaper is not willing to identiy the same since it is s standard idoc.
    Pls can you help as to w hy ship to 52004 and 56003 is missing in partner_id field and some other value 32500000789 is coming ? all other deliveries are created ok.
    rgds
    Pamela

    Hi Pamela,
    can you Please share some more information like IDoc details. so that v can analyze more.
    Regards,
    VSN

Maybe you are looking for