Creating own IDOC with segments

can any one let me know the steps to create <b>Z</b> IDOC and segments required for it.
and also the sample code (program) to poplulate the data into those segemnts from a (excel/csv file )or tables.
Thanks..

hi Aday,
There are basically two types of IDOCs.
Basic IDOCs
Extended IDOCs
Idoc Components
Basic Idoc
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extension Idoc
Extending the functionality by adding more segments to existing Basic IDOCs.
Creation of IDoc
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.
Create IDOC Type
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
Regards,
Naveen

Similar Messages

[IDOC] Creating own IDOC

Hey,
playing with IDOCs, I would like to create an own one with customized structure.
Found this thread:
Creating own IDOC with segments
In we31 I have to create a segment.
- Do you uses segment names longer than 7 characters? I would not
communicate with R/2 or older systems, so would you use longer names?
- Data elements: If you create your own IDOCs do you use own data elements?
Just want to have something like a string element. Or is there a standard
data element you can use? (sorry, a newbie question). I would like to use
S_PASSNUM, S_PASSNAME2, S_PASSNAME2......
thanks a lot.
chris
Edited by: Christian Riekenberg on May 21, 2008 2:54 PM

Hi Christian,
Data elements: If you create your own IDOCs do you use own data elements?
Its not mandatory that you have to create your own data element. You can use an existing data element.You must create new data elements in the following case:
A data element in SAP does not use one of the allowed data types for IDOC segments. For eg: the future price field (ZKPRS) in the E1MBEWM segment of the MATMAS02 basic type uses data type CHAR12 instead of ZKPRS. The reason is that the data type for ZKPRS is CURR (Currency) which is not allowed in a segment definition.
Reward points if helpful.
Regards,
Soumya.

Create multiple idoc with multiple receivers based on value mapping table

Hi,
Scenario:
Step1 : sender sends a finance doc iin the form of an idoc. This idoc will have multiple line items based on profit center. Do determine the value of receiving comp code(header field) n receiving system(logical sys name) value mapping table has to be used.
Solution so far: I can put an rfc lookup for fetching receiving comp code from mapping table with i/p paraameter as profit center . And split the incoming idoc based on comp code value by using split by value. Now I need your advise 2 take this further.
Issue 1 : say the incoming idoc has 4 line seg wid 4 diff profit center
Profit center.       Rec comp code.   Recv sys
P1.                       C1.                        R1
P2.                       C2.                        R1
PS.                       C2.                        R1
P3.                       C3.                        R2
Nw using this info, I want 3 diff idocs to be created for each unique comp code.
Idoc 1 : for C1 wid one line item + 1 for reconsilation ( to be generated additionally)
Idoc2 : for C2 wid 2 line items + 1 for reconsilation
Idoc 3: for C3 wid 1 line item + 1 for reconsilation
Idoc 1 and idoc 2 shud be sent to R1.
Idoc 3 shud be sent to R2.
Kindly advise on this

Hi experts,
U all r pretty close, but let me put this more clearly.
Step1: create multiple idocs based on unique comp code - I'm able to do this using rfc lookup n split by value. So I get 3 idocs each for c1, c2 n c3.
Nw as per the values from value mapping table.
Idoc for c1 contains 1 line seg.
Idoc for c2 contains 2 line segs.
N idoc for c3 contains 1 line seg.
steps2 n 3, where I do not have a confirmed solution yet n need ur advise.
Step 2 : for each idoc generated I need 2 create n additional segment, mapping 4 which will be based on the values in the original segments for that idoc.
In d above scenario, idoc for c1 contains 1 line seg, nw I want 2 add one more seg to it. The amount and pisting key values in this segment wud be calculated based on the values of the amount and posting key belonging to the original segment in this idoc.
Similarly for idoc for c2 there are 2 segs, nw I need one more, means 3 in allm
Hence for idoc for c3, 1 orig already present + 1 more. = total 2.
Nw I need ur advise on how 2 generate this additional seg in each idocm
Step 3: when all dese 3 idocs are generated, ( in this case itz 3, in real time it can be n), I need to find their respective receivers using rfc lookup n then based on the receiver send 2 resp recvng systm
Nw how do I do this?
Please explain with examples if possible 4 bettr understanding.
u2020ђąu03B7kўu03C3u03C5 in advance.

How to create Own IDOC

how to create our own idoc ..
plz help me with detail steps and explanations...
thanks in advance.

Hi Avi,
Please go through the blog updated by me.
http://theguruspeaksaboutsap.blogspot.com/2007/07/idoc-creation-steps.html
or go through this link
http://www.geocities.com/xplosion78/customised_ALE_IDOC_BY_SACHIN_DABHADE.zip
Reward if helpful.
Regards,
Harini.S

How to create New IDOC with refrence to existing IDOC.

Hello All,
In the MATMAS Material master data IDOC the special procurement type should consider the special procurement flag = VI also. At present the functional module IDOC_INPUT_MATMAS01 only take the special procurement flag = KA into account.
IDOC is in 05 status.
I want to Create a test IDOC copying the existing IDOC and change the SOBSL to VI to check if that is successful.
Please suggest,.
Thanks in advance.
Forum Shah

Hello,
I have made the changes with the partner profile.. WE20... and got the processing IDOC staus "03" ie "Translation ok".
how do i create a new IDOC to check if its working well?
Is there any need to add anything in the function module?

Edit the IDM Main Banner / Create own banner, with text and logo

I would like to edit/modify/customize the IDM Main Front-Page Banner, and replace it with my own text (possibly images, and/or company logo)
It's probably not possible to totally replace the *"Sun Microsystems Identity Manager"* banner. But, at least, I'd like to remove a part of it, and replace it with, say, my own custom text/image/, or my company logo.
How could I do this?

Hi
perhaps, I'm doing something wrong.
I have made modifications to the *"customStyle.css"* file, but nothing has any effect.
Should I be downloading this file from somewhere to somewhere? Or, should I be "commenting-out" some of the code in the file itself?
My IDM instance is simply ignoring the changes/modifications I am making to this file. Obviously, I am not doing something I should be doing.
Any tips, please?

How to create an IDoc just with the updated data.

Hello I have a question regarding IDocs.
In case I updated an existing material.
Is there a transaction where I can put a matnr in, that reads the change pointer table and creates an IDOC with just the updated fields for an existing material.
Like the transaction BD21, for example. But there I just have the possibility to enter a message type and not a material number.
If there is no standard transaction. What steps do I have to do to achieve this goal?
Kind regards,
Tobias

thanks a lot for your fast answers. but I want to decide weather I want to create a idoc that includes all data for a material (using transaction bd10) or create an idoc that includes just the updated data.
The program logic should be the following:
Select all materials in the change pointer table (that have been changed or new created).
Check what value has been changed.
If it is value YSAPSYSTEMXX (extension of mara) then create a idoc with all data for the material.
If not YSAPSYSTEMXX has been changed create an idoc that includes just the updated data.
For Idocs that include all material data I would use sap standard transaction BD10 and batch-input.
For Idoc that should only include the changed/updated data I am searching for a corresponding transaction.
Kind regards,
Tobias

How to create Inbound Idocs in a ABAP program? Any function Module?

Hello Experts,
My requirement is : I have sales order data which I extracted from third party system in my internal tables. In the same box I need to create inbound Idocs and then consequently create sales orders.
I have used the function module IDOC_INBOUND_WRITE_TO_DB to create inbound Idocs from Sales Orders data in internal tables. I have populated all the data records with correct PSGNUM and HLEVEL values. My plan is to create inbound idocs with this function module and send those to IDOC_INPUT_ORDERS function module which creates Sales Orders.
If a sales order in the internal table in ABAP program contains only one item, then I am getting correct idocs. But if more than one item exists for a sales order then the line item segments which got repeated in Idoc are having PSGNUM and HLEVEL values as zero when I checked in WE02. As a result the hierarchy from the second item segment is getting disturbed and getting the status 60.
I populated T_EDIDD with data records from IDOC_INBOUND_WRITE_TO_DB.
To the function module IDOC_INPUT_ORDERS, T_EDIDC and T_EDIDD are the input. I observed that in T_EDIDD also the PSGNUM and HLEVEL values are blank.
I am getting Status 60 with message 'EDI: Syntax error in IDoc (segment cannot be identified)' for idocs which have more than one item.
I need to extract sales data from third party and create inbound idocs and create sales orders in one ABAP program only. I need to display corresponding Idoc numbers for the corresponding third party sales order number in a listoutput.
Can anybody please provide inputs?
Regards.

Hi Anjali,
Thanks for the response.
I have passed the PSGNUM and HLEVEL values while populating the data records. Then I sent the data records and control record information to the function module IDOC_INBOUND_WRITE_TO_DB. Inside this function module there is code to clear the PSGNUM values and HLEVEL values.
for compatibility: clear administration data of data records
           perform data_records_wipe
                                  tables
                                      t_data_records.
FORM DATA_RECORDS_WIPE
                  TABLES
                      T_DATA_RECORDS_IN STRUCTURE EDIDD.
LOOP AT T_DATA_RECORDS_IN.
    CLEAR: T_DATA_RECORDS_IN-MANDT,
           T_DATA_RECORDS_IN-DOCNUM,
           T_DATA_RECORDS_IN-SEGNUM,
           T_DATA_RECORDS_IN-PSGNUM,
           T_DATA_RECORDS_IN-HLEVEL.
    modify t_data_records_in.
ENDLOOP.
ENDFORM.                               " DATA_RECORDS_WIPE
This is the code which is clearing all the PSGNUM and HLEVEL values. After coming out of this function module we are getting the error idocs created with disturbed hierarchy.
I need to create INBOUND Idocs with the data in ABAP program.
Please let me know if any inputs? Is there any function module existing to create Inbound Idocs inside an ABAP program?
Regards

How to generate PAYEXT (PEXR2002) IDOC with many invoices for same vendor

Hello,
We are implementing the IDOC payment processing through transaction F110. The first test we ran using multiple items for the same vendor created an IDOC with multiple E1IDPU1 segments for each invoice. We then configured a second bank and ran the test again. This time the multiple invoices for the same vendor generated a seperate IDOC.
Does anyone know where I should start looking to figure out what I did wrong? We are hoping to generate 1 IDOC for all invoices for the same vendor.
Thanks,
Brian

Hello,
May I know how or what are the steps you did to create multiple invoices and generate multiple idocs for the same vendor? I have a requirement to generate multiple payext idoc for a single vendor.
Please advise. Thank you very much!

How to Test, Inbound idoc ,with out the Sender System, using a Text File

Hi Guru's .
we wanted to test BLAORD03 inbound idoc (Message Type BLAORD).with out the SENDER SYSTEM.
on the same client.
we wanted to test this idoc with text file from our local machine.
Can anyone give us detail steps.like how to create File layout
with Segment name,and values for the fields.how to pass this file to the system.
Thanks in advance.

Hi Aparna.
My requirement is to test the idoc with Inbound File.
Generate a file with the data entered through segments through we19 ,and use the same file for processing through we16.
when i am trying to do this syst complaing about
Partner Profile not available, and some times
port not available. and some times with
'No further processing defined'.
but i maintained part profiles and port perfectly.
Can you help me in testing with test 'File' port.

ALE , EDI and IDOC with MM??

hii
What is ALE, EDI and IDOC in SAP??
How its linked with MM??
Explain the above things with example
Thanks

Hi!
IDOC = Intermediate Document
IDoc or Intermediate Document is a standard SAP document format. IDoc's allow different application systems to be linked via a message-based interface.
For more detailled information look in SAPNET under
http://service.sap.com/EDI
For exapmle in purchasing:
The IDoc message type ORDERS is used to send a purchase order to a vendor.
EDI = Electronic Data Interchange
EDI stands for Electronic Data Interchange, which means that data is electronically transmitted from one system to another. The main requirement of EDI is that the systems of the communicating partners understand each other. Usually, the data from one partner gets mapped into the format of the other partner and vice versa.
Supporting this there exist EDI standards (named EDIFACT, ANSIX12, ODETTE, VDA, TRADACOMS, SPEC2000, ...), where the data formatting for exchanging documents are specified. Normally the partners agree using a special standard message (for example EDIFACT message ORDERS for a purchase order).
In the SAP system the outgoing data are stored in IDoc format. When processing a receiving document, the Inbound SAP system receives the data in IDoc format too.
Further processing (converting/mapping from IDoc in another format and vice versa) depends on the partner agreement:
If the partners have agreed using a special EDI standard, mapping between IDoc and the EDI standard is necessary. This mapping is not supported by SAP, external converters or EDI subsystems must be installed by the customers for this purpose.
If both systems use SAP software, there is usually no need for mapping (which can save users a lot of money). The two systems are often connected via ALE (Application Link Enabling).
If partners are using XML, the SAP Business Connector can be used. The business connector is a tool used to help customers connect via EDI. It includes routing and mapping and is XML compatible. To read more about XML at SAP go to SAPNet Alias 'XML' (http://intranet.sap.com/XML).
For example:
Vendor can send the invoice by EDI creating an IDoc with message type INVOIC using IDoc Type INVOICxx. He can determine (depending on the partner agreement) how to create an IDoc for Inbound processing with FI or MM-IV.
ALE = Application Link Enabling
ALE is short for Application Link Enabling. Special Basic programs support this functionaliity (see documentation of BC_MID_ALE).
To link applications you have to configure an ALE model. It contains all relevant data about how a system's configuration (normally a central system and assigned local systems) exchange data.
With help of the ALE technology, the distribution of contracts is possible in MM via the following business process:
Contracts that a central purchasing organization distributes to local purchasing organizations to allow the latter to utilize the more favorable conditions they contain for the procurement of materials or external services.Each local purchasing organization sends information on its own release orders back to the central purchasing organization.
For this purpose the contract in the central system can be copied to the local systems (with message BLAORD and COND_A). When a release order to a distributed contract is created in a local system, the release docu is automatically sent to the central system (with message BLAREL) updating the release docu of the contract in the central system.
Precondition for this scenario is, that in all systems the used master data (material, vendor, sources of supply, ...) are the same. This master data can be distributed by ALE, which should be done before sending the contract from the central system. Available message types for distribution of master data are:
MATMAS (ARTMAS in retail system) for material master
CREMAS for Vendor master
INFREC for info record
SRCLST for source list
COND_A for conditions of info record
SRVMAS for service master data
Technical documentation to ALE can be found by path:
Basis Components / Middleware (BC-MID) / Application Link Enabling (BC-MID-ALE)
The most important Transactions for testing Idoc:
WE02 Display IDOC
WE05 IDOC list
WE19 Testing IDOCs
BD87 Status Monitor for ALE Messages (reprocess)
Notes:
456127 FAQ: Electronic Data Interchange (EDI) in Purchasing
536411 Sample scenario for ALE contract distribution (only internally released)
I hope I could help you fruther
Best regards
Erika

Standard program for creating outbound IDoc holding wbs+cost plan

Hello,
a)
Before we start developing our own ABAP, I would like to ask the forum if somebody knows if there is already a standard ABAP program for generating outbound IDocs including wbs-element data (CJ20N; wbs ID, description) plus annual data from the cost planning (CJ41; such as fiscal year and costing items from unit costing; quantity, unit, price per unit, total price, description of item) ?
b) we are planning to use the logical message /ISDFPS/PS, basic type /ISDFPS/PS01 and enhance this IDoc with segments for the costing items from the cost planning.
Question: Do you know if there is a standard IDoc which has segments for both wbs-element data and costing items?
Kind regards
Viveka Schwartz

Hi Frank,
Did u check this Link on the PP confirmaitos[LINK|http://help.sap.com/saphelp_47x200/helpdata/en/12/3bbc1c504811d182c20000e829fbfe/frameset.htm]
Reg
Dsk
Edited by: DSk on Sep 14, 2010 3:44 PM

Standard program for creating outbound IDoc including wbs + cost planning

Hello,
a)
Before we start developing our own ABAP, I would like to ask the forum if somebody knows if there is already a standard ABAP program for generating outbound IDocs including wbs-element data (CJ20N; wbs ID, description) plus annual data from the cost planning (CJ41; such as fiscal year and costing items from unit costing; quantity, unit, price per unit, total price, description of item) ?
b) we are planning to use the logical message /ISDFPS/PS, basic type /ISDFPS/PS01 and enhance this IDoc with segments for the costing items from the cost planning.
Question: Do you know if there is a standard IDoc which has segments for both wbs-element data and costing items?
Kind regards
Viveka Schwartz

Hi Frank,
Did u check this Link on the PP confirmaitos[LINK|http://help.sap.com/saphelp_47x200/helpdata/en/12/3bbc1c504811d182c20000e829fbfe/frameset.htm]
Reg
Dsk
Edited by: DSk on Sep 14, 2010 3:44 PM

Vendor Master Creation through IDoc with Multiple Company Codes

I am trying to create vendor masters sent from a 3rd party into SAP using CREMAS05 IDoc. I have the requirement that the vendor should be created in each of 3 company codes and the vendor number is internally assigned in SAP.
I create my IDoc with the general data E1LFA1M and multiple E1LFB1M & E1LFB5M Children. When I post the IDoc using IDOC_INPUT_CREMAS which uses Call Transaction, the vendor gets created for the first company code, but the IDoc errors on the vendor extension XK01 for the next company code with the error: "Fill all required fields SAPMF02K 0111 ADDR1_DATA-NAME1".
In debugging through this, it appears that the vendor number that gets created in the first XK01 transaction does not get passed into the data for the second XK01 call and SAP tries to create a new vendor instead of extending the newly created one.
If I force the value in during debug after the initial call transaction into the variable h_lifnr, it works fine (Vendor created with multiple company codes.
Any help would be greatly appreciated.
-Larry

I cannot give you exact solution, but can guess why this is happening, below is what I believe.
I think Synchronous update is not happening in call transaction, second transaction is getting processed before the first one is saved, debugging it works fine, because we give system enough time to save while processing.
Generally in call transaction we have MODE, if we pass S - then synchronous update happens, in your case, you need to find the way to incorporate this.
Hope it helps.
Regards,
Ravi Kishore.

IDOC with ALV report

Hi All,
i written a program for IDOC its generating idoc succesfully,
now my requirement is to create an IDOC with ALV report.
this is new to me, so pls kindly give some sample code to generate an IDOC with ALV report.
regards,
Msrinu.

Hi ,
this is my outpt internal table, from this i want idoc no,cust no,cust name,EAN,net price,guebg,currrency thsese fields i want to produce as ALV report. this is i written in se38 as standlone program for generating an idoc.
BEGIN OF gt_output,
        idoc       LIKE edidc-docnum,           "M01
        kunnr(10)        TYPE c, "Customer Number 1
        addrnumber(10)   TYPE c, " Address No
        name1(40)        TYPE c, " Customer Name
        name2(40)        TYPE c, " Customer Name
        street(60)       TYPE c, " Street
        str_suppl2(40)   TYPE c, " Address
        str_suppl3(40)   TYPE c, " Address
        city1(40)        TYPE c, " City
        post_code1(10)   TYPE c, " Postal Code
        region(3)        TYPE c, " Code identifying County
        country(3)       TYPE c, " Code identifying County
        tel_number(30)   TYPE c, " Telephone
        matnr(18)        TYPE c, " Material no.
        werks(4)         TYPE c, " Werks
        netpr(11)        TYPE c, " Net price
        waerk(5)         TYPE c, " Document Currency
        vbeln(10)        TYPE c, " Sales Document No
        knumh(10)        TYPE c, " Condition record number
        kopos(2)         TYPE c, " Sequential number of the condition
        konwa(5)         TYPE c, " Rate unit (currency or percentage)
        kbetr(11)        TYPE c, " Rate
        kpein(5)         TYPE c, " Condition pricing unit
        kmein(3)         TYPE c, " Condition unit
        ean11(18)        TYPE c, " International Article Number (EAN/UPC)
        kdmat(35)        TYPE c, " Material Number Used by Customer
        kappl(2)         TYPE c, " Application
        kschl(4)         TYPE c, " Condition type
        datbi(8)         TYPE c, " Validity end date of the condition record
        datab(8)         TYPE c, " Validity start date of the condition record
        guebg(8)         TYPE c, " Valid-from date
        gueen(8)         TYPE c, " ValiD-to date
        eikto(12)        TYPE c, " Supplier number
        cunit(5)         TYPE c, " Consumer unit
     END OF gt_output,
regards,
msrinu.

Creating own IDOC with segments

Similar Messages

Maybe you are looking for