Materials for idoc

Hi am interested to learn about idocs can you provide me some useful links

Hi saranya srithar ,
IDoc is an Intermediate document that holds application data.
A container used to exchange data
It is independent of the complex SAP structure to store data.
It serves as the vehicle for data transfer.
IDoc Type defines the structure and format in which the data is exchanged.
It is similar to a structure in SAP
IDoc data is an instance of IDoc Type
IDoc acts as a standard SAP interface to exchange business data through ALE.
From an SAP system, an IDoc can be sent to and received from
An SAP R/3 system
An SAP R/2 system
An EDI subsystem
Any third-party application software
Segments . Idoc data is arranged in Rows, The rows make up segments of an idoc. Each segment consists of fields/segments. Fields can contain data.
These r all the t/codes which we will come across in IDocs:
TCODE     TTEXT
BD10     Send Material
BD100     IDoc display object channel view
BD101     Consistency check
BD102     Outbound registry
BD103     Inbound registry
BD104     maintain tbd53
BD105     Maintain Supported Business Objects
BD11     Get Material
BD12     Send customer
BD13     Get customer
BD14     Send vendor
BD15     Open vendor
BD16     Send Cost Center
BD17     Get Cost Center
BD18     Send General Ledger Account
BD19     Get General Ledger Account
BD20     IDoc passed to application
BD21     Select change pointer
BD22     Delete change pointers
BD23     Delete serialization data
BD24     Send Cost Elements
BD25     Send Activity Type
BD26     Get Activity Type
BD27     Send cost center activity prices
BD28     Send obj/cost element control data
BD30     Distribute material object list
BD31     Distribute document object list
BD32     Distribute plant allocations(matBOM)
BD33     Distribute material variants (ALE)
BD34     Distribute order BOM
BD35     Send Business Process Groups
BD36     Send Business Processes
BD37     Send Business Process Price
BD40     Read change pointer for group
BD41     Dispatch IDocs for group
BD42     Check IDocs for group
BD43     Post IDocs for group
BD44     Assign Message Types to Serlz. Group
BD47     Dependencies between methods
BD48     Dependency method - message
BD50     Activate Change Ptrs for Mess. Type
BD51     Maintain function modules (inbound)
BD52     Activ.change pointer per chng.doc.it
BD53     Reduction of Message Types
BD54     Maintaining Logical Systems
BD55     Maintain IDoc Conversion
BD55OLD     Maintain IDoc Conversion
BD56     Maintain IDoc Segment Filters
BD57     Maintain link and serialization ty.
BD58     Convert organizational units
BD59     Allocation object type -> IDoc type
BD60     Additional data for message type
BD61     Activate Change Pointers - Generally
BD62     Define Segment Conversion Rule
BD62OLD     Define Segment Conversion Rule
BD63     Transport ALE Tables of Message Type
BD64     Maintenance of Distribution Model
BD65     Maintain IDoc type required fields
BD66     IDoc type field -> change doc.field
BD67     Maintain methods (inbound)
BD68     Maintain Lists
BD68OLD     Maintain Lists
BD69     Assignment of Message Type to IDoc
BD70     Synchronize Number Ranges
BD71     Define FM for dependent bus. object
BD72     Activate Events
BD73     Reposting of IDocs (ALE)
BD75     Convert IDoc Status
BD77     Distribution of control data
BD78     Monitoring control data distribution
BD79     Maintain IDoc Conversion Rules
BD79OLD     Maintain IDoc Conversion Rules
BD81     Filter objects parameter filtering
BD82     Generate Partner Profiles
BD83     Send IDocs after an ALE error
BD84     Post IDocs after ALE error
BD85     Consistency check for transfer
BD86     Consistency check for sales
BD87     Status Monitor for ALE Messages
BD89     Control data model. - initial screen
BD91     Send Characteristic
BD92     Send Class
BD93     Send Classification
BD95     Specify ALE object types
BD96     filter objects of receiver determin.
BD97     Assign RFC dest. to Logical Systems
BD98     Consistency Check Workflow Connectn.
BD99     Message type dependencies
WE02     Display IDoc
WE05     IDoc Lists
WE06     Active IDoc monitoring
WE07     IDoc statistics
WE08     Status File Interface
WE09     Search for IDocs by Content
WE10     Search for IDoc in Archive
WE11     Delete IDocs
WE12     Test Modified Inbound File
WE14     Test Outbound Processing
WE15     Test Outbound Processing from MC
WE16     Test Inbound File
WE17     Test Status File
WE18     Generate Status File
WE19     Test tool
WE20     Partner Profiles
WE21     Port definition
WE23     Verification of IDoc processing
WE24     DefaultValuesForOutboundParameters
WE27     DefaultValues for Inbound Parameters
WE30     IDoc Type Development
WE31     Development IDoc Segment
WE32     Development IDoc View
WE34     Object for Display of XML IDocs
WE40     IDoc Administration
WE41     Process codes, outbound
WE42     Process codes, inbound
WE43     Funct.module: Status record display
WE44     Partner Types and Checks
WE45     Forward (inbound) (V3, EDILOGADR)
WE46     Error and Status Processing
WE47     Status Maintenance
WE50     System process codes: Texts
WE51     System process codes: Change texts
WE54     FMs for changing file names
WE55     Function Module for Path Names
WE56     IDoc Administration
WE57     Assignment Messages for Appl. Objs
WE58     Status process codes: Texts
WE59     Change status process codes
WE60     Documentation for IDoc types
WE61     Documentation for IDoc record types
WE62     Documentation for segments
WE63     Documentation
WE64     Documentation message types
WE70     Conversion: Basic types
WE71     Conversion: Extensions
WE72     Conversion: IDoc types
WE73     Conversion: Logical messages
WE81     Logical message types
WE82     Assign Messages for IDoc Type
WE84     Assignment of IDoc and appl. fields
WE85     Create Rule Names
WEBU     Printing Labels via Assortment List
WEDI     EDI Basis
WEINBQUEUE     IDoc Inbound Queue
WEKF     Purchase order SAP Retail
WEL0     Forward (inbound) (EDILOGADR)
WEL1     EDI: Interface Invoice for EDILOGADR
WELI     Maintain Status Groups
cheers!
gyanaraj

Similar Messages

Learning Materials for ALE and Idocs

Hi Experts,
Kindly send me the documents/Links for ALE and IDocs.
Regards,
Ram.

Hi
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
check these...
http://www.onestopsap.com/interview-Question/ale/
http://sap.ittoolbox.com/groups/career/sap-career/aleidoc-interview-questions-688290
http://www.erpgenie.com/faq/ale.htm
Outbound:
Step 1. Application document is created when transaction is saved.
         2. Message control is invoked.
         3. Messages are processed by system.
         4. Messages are Edited (if desired).
         5. Output (ALE / EDI) is checked
         6. Validate against Message control record from Partner Profile
         7. Application Document is saved.
         8. Entry NAST table is created for every selected output program
              along with Medium & Timing.
         9. Check for Process Immediately .
                 If (yes)
                   Determine Processing Program from TNAPR Table.
                 ELSE
                   Execute RSNASTED Program.
       10. Read Partner Profile to determine Process Code.
       11. Process Code points to the Function Module & Invoked.
       12. IDoc is generated.
       13. Check for ALE Request.
                    if (Yes)
                        Perform Filters, Conversions, Version Changes etc.
                    Else.
                        IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
        2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
         3. Data in Control Record is validate against the Partner                       Profile.
        4. IDoc is generated in Database and syntax check is                      carried out.
        5. IDoc file is deleted once file read.
        6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
                   7. Check for Process Immediately.
               If NO
                 Execute RBDAPP01 Program
               Else
                  Read Process Code from Partner Profile
                       Process Code Points to Function Module
                 Application Document Posted.
further help:
IDOC
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
Reward points if useful
Regards
Anji

Program logic for IDoc

hi everyone,
I am new to IDoc. Through some forums i came to know that we need to create
segment in we30
idoctype in we31
i understand the above two
msgtype in we80
attaching msgtype to idoctype in we81
i didnt understand how to do the above two, and also i want to know what to do next..like how to do the program
my mailID is [email protected](for any materials if u have)
Regards,
Venkata
Points will be rewarded to answers given
Message was edited by:
        venkata k

One very simple code:
==============================
*abap program to generate a customized idoc and send it to the target *system.
REPORT z_b8_ale .
TABLES : ekko,ekpo.
***Data Declaration for IDOC Begin
DATA : v_master_control LIKE edidc.
DATA : BEGIN OF int_idoc_data OCCURS 0.
        INCLUDE STRUCTURE edidd.
DATA : END OF int_idoc_data.
DATA : BEGIN OF int_comm_control OCCURS 0.
        INCLUDE STRUCTURE edidd.
DATA : END OF int_comm_control.
DATA : BEGIN OF itab OCCURS 10,
       lifnr LIKE ekko-lifnr,
       ekorg LIKE ekko-ekorg,
       ekgrp LIKE ekko-ekgrp,
       kdate LIKE ekko-kdate,
       ematn LIKE ekpo-ematn,
       ktmng LIKE ekpo-ktmng,
       meins LIKE ekpo-meins,
       netpr LIKE ekpo-netpr,
       werks LIKE ekpo-werks,
       peinh LIKE ekpo-peinh,
       END OF itab.
DATA : str LIKE edidd-sdata,
       sagrnum(10) TYPE c VALUE '5500000019'.
DATA:itab1 LIKE ekko OCCURS 0 WITH HEADER LINE,
     itab2 LIKE ekpo OCCURS 0 WITH HEADER LINE.
***Data Declaration for IDOC End
****FILL_MASTER_CONTROL
CLEAR v_master_control.
v_master_control-rcvpor = 'ZPORTB8'.
v_master_control-rcvprt = 'LS'.
v_master_control-rcvprn = 'D12503'.
v_master_control-mestyp = 'ZSCHB5'.
v_master_control-idoctp = 'ZSCHIDOC'.
****FILL_IDOC_DATA
CLEAR int_idoc_data.
REFRESH int_idoc_data.
int_idoc_data-segnam = 'ZSCHDLAGR'.
SELECT single * INTO itab1 from ekko WHERE ebeln = sagrnum.
SELECT single * INTO itab2 from ekpo WHERE ebeln = sagrnum.
MOVE itab1-lifnr TO str+0(10).
MOVE itab1-ekorg TO str+10(4).
MOVE itab1-ekgrp TO str+14(3).
MOVE itab1-kdate TO str+17(8).
MOVE itab2-ematn TO str+25(18).
MOVE itab2-ktmng TO str+43(16).
MOVE itab2-meins TO str+59(3).
MOVE itab2-netpr TO str+62(13).
MOVE itab2-werks TO str+74(5).
MOVE itab2-peinh TO str+80(5).
int_idoc_data-sdata = str.
APPEND int_idoc_data.
write : / str.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
     EXPORTING
          master_idoc_control            = v_master_control
     TABLES
          communication_idoc_control     = int_comm_control
          master_idoc_data               = int_idoc_data
     EXCEPTIONS
          error_in_idoc_control          = 1
          error_writing_idoc_status      = 2
          error_in_idoc_data             = 3
          sending_logical_system_unknown = 4
          OTHERS                         = 5.
COMMIT WORK.
WRITE : / 'IDOC Number created : ', int_comm_control-docnum.
Regards,
Gajendra.

User exit for IDOC in INVOICE

Hi all,
I need to add a value in a custom IDOC segment for INVOICE. The IDOC basic type used is INVOIC02. Is there any user exit which I can use to populate the IDOC data? Any help will be greatly appreciated.
Thanks,
Lalyn

Hi Lalyn,
I do not have an exact code for this.
But just go through the following code, where we are doing some validations in the segments.
Code below this line was to exclude ZRTN materials for which Subtotal 2 (KZWI2) is zero. And,
this is done for billing types:
                               ZEXP,
                               ZXAD,
                               ZXDR,
                               ZXL2,
                               ZXG2,
                               ZXPT.
IF INT_EDIDD-SEGNAM = 'E1EDS01'.
ZE1EDS01 = INT_EDIDD-SDATA.
IF ZE1EDS01-SUMID = '001'.
Start deleting when on 1st E1EDS01 segment
    DESCRIBE TABLE INT_EDIDD LINES POS.
    LOOP AT XTVBDPR.
      CLEAR MARA.
      SELECT SINGLE MTART MATKL FROM MARA INTO            "DV2K920646
      (MARA-MTART,MARA-MATKL)                             "DV2K920646
      WHERE MATNR = XTVBDPR-MATNR.     " Find material type MTART
      IF XVBDKR-FKART EQ 'ZEXP' OR XVBDKR-FKART EQ 'ZXL2' OR
         XVBDKR-FKART EQ 'ZXAD' OR XVBDKR-FKART EQ 'ZXG2' OR
         XVBDKR-FKART EQ 'ZXDR' OR XVBDKR-FKART EQ 'ZXPT'.
        IF MARA-MTART = 'ZRTN' AND XTVBDPR-KZWI2 EQ 0
         AND MARA-MATKL <> 'KEGS DM'.                  "DV2K920646
          MOVE XTVBDPR-POSNR TO POSNRS-POSNR.
          APPEND POSNRS.               " Store ZRTNs to be deleted
        ENDIF.
      ENDIF.
    ENDLOOP.
    DESCRIBE TABLE POSNRS LINES COUNT.
Reduce the number of line items by the number of them to be deleted
    ZE1EDS01-SUMME = ZE1EDS01-SUMME - COUNT.
    SHIFT ZE1EDS01-SUMME LEFT DELETING LEADING SPACE.
    INT_EDIDD-SDATA = ZE1EDS01.
    MODIFY INT_EDIDD INDEX POS TRANSPORTING SDATA.
    LOOP AT INT_EDIDD INTO IEDIDD.     " Loop and delete if in POSNRS
      IF IEDIDD-SEGNAM = 'E1EDP01' OR IEDIDD-SEGNAM = 'E1EDS01'.
        CLEAR DELETE_FLAG.
      Reset delete_flag when on next line item or done with all
      ENDIF.
      IF IEDIDD-SEGNAM = 'E1EDP01'.
        ZE1EDP01 = IEDIDD-SDATA.
        READ TABLE POSNRS WITH KEY POSNR = ZE1EDP01-POSEX.
        IF SY-SUBRC EQ 0.
          DELETE_FLAG = 'X'.
        Set delete_flag if the line item is to be deleted
        ENDIF.
      ENDIF.
      IF DELETE_FLAG = 'X'.            " Delete the line item fully
        DELETE INT_EDIDD.
      ENDIF.
    ENDLOOP.
ENDIF.
ENDIF.
At this function module, you have to create an include and write your code.
But remember, before that you have to extend your basic type.
Hope it will help you.
sailesh

Problem creating basic views while creating materials using idocs?

hello,
I am facing an issue while creating materials using idocs. The problem is that the basic view does not get created whereas other views are present. The function module used is idoc_input_matma01 and the basic idoc type is MATMAS03.
Looking for help. Thank you

Hi Madhu,
Actually i recieve an idoc from PI containing data required for cretion of the material via an idoc. This idoc is then processed to create the required material.
The material gets created with appropiate data in various tables(mara, makt) but when we view material in mm03 we cant see the basic data views.

Trigger condition for IDOC

Hi,
I have trigger condition for IDOC
All materials where:
"Finished Goods" Technical Names MARA-MTART = "Z001", and the Plants are "Granollers" MARC-WERKS="ES11", MARC-WERKS="ES12", goods that are "ready" or "ready for manufacturing", MARC-MMSTA = "02" or "03".
All the materials which satisfy this criteria will need to be triggered whenever a new material is created in SAP which meets the above criteria, or if any materials are modified which meet the above criteria in SAP.
How do I trigger my IDOC based on these conditions.
Regards,
Subhashini

Hi,
Please create the Idoc type / segments , create message type and link Idoc and message.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
2. Yes, you need LS & Partner profile
3. Yes use MASTER_IDOC_DISTRIBUTE
4. Can use IDOC_CREATE_ON_DATABASE instead of MASTER_IDOC_DISTRIBUTE and then process the Idoc.
Message Type :: The message type defines the semantic context of an IDoc. The message type tells the processing routines, how the message has to be interpreted. The same IDoc data can be sent with different message types.
IDoc Type :: An IDoc type defines the syntax of the IDoc data. It tells which segments are found in an Idoc and what fields the segments are made of.
Processing Code :: The processing code is a logical name that determines the processing routine. This points usually to a function module, but the processing routine can also be a workflow or an event.
The use of a logical processing code makes it easy to modify the processing routine for a series of partner profiles at once.
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.
thanks & Regards,
ShreeMohan

Help in creation of XML file for IDOC postings

Hi All,
Need help if anyone has knowledge/experience in creating XML files for IDOC processing.
We need to design an input file (in XML format) for creation of IDOCu2019s for purchase Invoices through Interface.
We have an existing input file, which is working correctly. We are trying to modify this existing input file for a new Tax Code (Non-deductible inverse tax liability). This tax code is working fine for manual postings. But, through IDOC, tax postings are not correctly triggering.
Could you please confirm if any one has experience on this, so that I can share more details for resolving.
Thanks & Regards,
Srini

Hello,
you can use CALL TRANSFORMATION id, which will create a exact "print" of the ABAP data into the XML.
If you need to change the structure of XML, you can alter your ABAP structure to match the requirements.
Of course you can create your own XSLT but that is not that easy to describe and nobody will do that for you around here. If you would like to start with XSLT, you´d better start the search.
Regards Otto

Mandatory Fields for IDOC ORDERS01 for Pricing Condition EDI1 to trigger

Hi ,
I'm Testing an Inbound ORDRSP using we 19 for Pricing Conditions EDI1. What are the Mandatory Fields for IDOC ORDERS01
Thanks

hello,
I think it's better to execute VA01 to create a sales order; in that way you should have an idea of mandatory fields.
Thanks.

MATERIAL LINK TO ONE SAP SYSTEM TO ANOTHER SAP SYSTEM FOR IDOC TRANSFER

Hi Experts,
How the MATERIAL LINK TO ONE SAP SYSTEM TO ANOTHER SAP SYSTEM FOR IDOC TRANSFER?
Scenario : when 2nd system create the invoice,it will create a po in the 1st system.
51 error msg we are getting material does not exists.but the material is available in the receiving plant.
Please suggest

If you say the material master is available in the 1st system (where you create the order), then the material number in the IDOC may not match with the material number in your database.
leading zeros. material number stored as alphanumeris instead of numeric.

Business system for idoc reciver communication channel.

hi gurus,
iam doing one file to idoc scenerio.
for defining reciver idoc adapter ,which type of businees system i required that is configured in SLD.
pls guide me .
warm regards.

Hi
You can use th Buiness system as a receiver for IDOC.
Making sure
1. the LS of the system(R/3) is same in the SLD and it is also reflecting in the adapter specific attributes in the ID.
2. Use the same LS name for the BS pointng to FIle in the SLD.
Complete the IDOC configuration from XI
1. Create the RFC dest from XI to ECC
2. Create the Trfc port and call this RFC dest created..
3. Use this Trfc port in the IDOC receiver
On ECC:
Make sure the Partner Profiles is created properly.
it is suggested to use always the business systems when you deal with IDOC and Proxies.
Edited by: Nisar Khan on Feb 27, 2008 1:31 PM

Issue loading Meta Data for IDoc Type WPUKSR01 in XI Integration Repository

Hi,
I want to load the Meta Data for IDoc Type WPUKSR01 in XI Integration Repository out of BI. Unfortunately, this IDoc is not available in the IDoc List. I checked in BI and the IDoc Type is available in WE60 and WE30. Also, I can load the Meta Data for the Idoc in XI ABAP (IDX2).
Can someone tell me why the IDoc doesn't show up in XI Integration Repository Import Object List?
Thanks in advance.
Best Regards.
Alex

Hi Aamir,
The Idoc is released since Release 30A. I also tried to load the IDoc Meta Data from ERP with the same result: it does not show up in the list.
Thanks anyway.
Alex

EOIO for IDOCs to XI

Hi,
My scenario is IDOC ---> xi ---> File.
Need to implement EOIO(serialization) for IDOCs coming from ECC.
Checked "Queue Processing" and assigned rule "FIRST_16_OF_MESTYP".
When I send the IDOC using WE19, I get message "IDocs are stored in the queue".
But, IDOCs are not coming to XI. Please help.
Versions: ECC 6.0 & PI 7.0 SPS 13.
Also, do I need to maintain an entry in IDXQUEUE table?

Hi
use similar thread
How to implement IDOC Serialization(EOIO) using IDOC Adapter
Re: Posting idocs in sequence in SAP from file (without BPM)

SA PI 7.1 EHP1 - Support for IDOC Adapter using AAE

Hi,
Can anyone confirm if the SAP PI 7.1 EHP1 supports the IDOC adapter in the AAE ?
Cheers
Colin.

Hi Colin,
I am workinngt on EHP1 PI7.1,but no support for IDoc Adapter in the AAE.
The new features added for IDoc adapter is IDoc packging and new conversion module added .
we have to wait till next release,but not sure...
Regards,
raj

Abstract Interface for IDoc Proxy

Hi All,
Do we need to make Abstract interfaces for IDocs and Proxys too if we want to use them in BPM?
XIer

Aamir,
I agree with u that we can't create proxie's for Abstract interfaces. But consider the case I want to call Proxy inside BPM, is this possible?
Yes its possible. As I mentioned in my previous replies for IDOC's .Similarly for Proxy receiver Interface determination we need to give Actual Inbound Interface name instead of Abstract. MI_Proxy_Abs --> use MI_Proxy_IB . Provided both the interfaces has the same structure.
I hope it clears!!!
Best regards,
raj.

Error : Pre Settings for IDoc inbound processing are missing error

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

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

Materials for idoc

Similar Messages

Maybe you are looking for