Creating a new IDoc

Dear all ,
I need to create an IDoc for testing in quality enviroment.
I do not have any IDoc with the same Message type to copy from . How do I go about that ??
Thanks in Advance ,
Vivek K .

here is the procedure to define new IDoc type
Define Segments                       WE31
Create IDoc type and attach segments WE30
Release Segment                       WE31
Release IDoc Segment                  WE30
Define a logical message              WE81
Attach IDoc type to logical message   WE82
for an example with screen shots have look at
http://www.allsaplinks.com/idoc.html

Similar Messages

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?

Is it possible to create a custom IDOC status?

Is it possible to create a custom idoc status on table TEDS1?
I have looked through customising and cannot seem to find a way to create a new idoc status.
Has anybody done this?

Hello Chester..
hope this link will be helpful,
Re: IDOC status
*********Please reward points ,if found useful

How can I get a new IDOC number?

Hi,
I have developing a method to send IDOCs from non-SAP system to SAP but I have a doubt:
-When non-SAP system creates a new IDOC to send it to SAP, what IDOC number can use? I think it's mandatory otherwise how can make a relation between IDOC_CONTROL_REC_40 and IDOC_DATA_REC_40 ?
Best regards,

Can you describe the problem in more detail (without giving us your serial number)?
Exactly what version of LR are you running, the LR on the CD, or a downloaded copy? If downloaded, are you sure it is LR5, and not the Creative Cloud version? Where did you purchase this version of LR 5?
Have you tried these steps? Find your serial number quickly

File2IDoc - new IDoc when client-number in sub-segment of MT is different

Hi, we have an Message-Type and IDoc with four different Segments. Each of it contains a client-number.
First segment: Header
Second-fouth: Childs
When i read File via FTP in XI it could happen that the Header-Segment is not depending on the child. That is when the client-number in the text-file is different. When this happens, XI should create a new IDoc where no Header-Segment will occur.
How should i manage this in mapping? i have to read the payload and must compare the client-number of each child in the txt-file.
Could you give me some help?!
This is the source-structure:
<?xml version="1.0" encoding="UTF-8"?>
<MT_BESTFILE>
   <BestfileRecordSet>
      <BestFileHeader>
         <BDKDNR/> (=client-number)
      </BestFileHeader>
      <BestFilePos>
         <BDKDNR/>(=client-number)
      </BestFilePos>
      <BestFilePos1>
         <BDKDNR/>(=client-number)
      </BestFilePos1>
      <BestFilePos2>
         <BDKDNR/>(=client-number)
      </BestFilePos2>
   </BestfileRecordSet>
</MT_BESTFILE>

Hi Carsten,
Below UDF will solve your problem,
Here it will take input as BDKDNR from Header, Pos, Pos1 and Pos2, and output should be mapped to IDOC Header so that it will create a new idoc when ever there is a change in child segment.
as per your query it is clear that BDKDNR from header will match with child segments but some times it will differ at that point we should create a new IDOC.
in the UDF header BDKDNR will be compared to the child BDKDNR's if it is not matching with the header then it will create a new idoc.
Please let me know it the problem still exits.
public void test(String[] header,String[] pos,String[] pos1,String[] pos2,ResultList result,Container container){
int i,j,count=0;
for(i=0;i<header.length;i++)
result.addValue(header<i>);
for(j=0;j<pos.length;j++)
    for(i=0;i<header.length;i++)
     if(!(pos[j].equals(header<i>)))
     count++;
   if(count>0)
   result.addValue(pos[j]);
   count=0;
for(j=0;j<pos1.length;j++)
   for(i=0;i<header.length;i++)
    if(!(pos1[j].equals(header<i>)))
     count++;
if(count>0)
   result.addValue(pos1[j]);
   count=0;
for(j=0;j<pos2.length;j++)
   for(i=0;i<header.length;i++)
if(!(pos2[j].equals(header<i>)))
     count++;
if(count>0)
   result.addValue(pos2[j]);
   count=0;
Regards,
Karan

A new IDOC status - ex. 80

Is it possible to create a new IDOC status code? we want to capture some of the intermediate processing messages in the IDOC status log. ex. "status 80 - BDC x done" -> "Status 80 order created" -> "Status 53 order has been imported".
I couldn't find anything under SALE but did saw couple of tables that list out status numbers and associated texts w/ it. I thought I would be able to add in a new status number - code, but 'new entries' is not an option.
Thanks in advance.

Yes, you have an option to create new status messages. I have done this before.
Please try running the area menu WEDI from your SAP easy acess screen.
You will find an option to create new status.
Let me know if you need more details.
Regards
Sabu

IDOC_INBOUND_ASYNCHRONOUS FM not creating new IDOC?

Hi,
IDOC_INBOUND_ASYNCHRONOUS function module is not creating new IDOC in SAP.
I configured all related functions against message type and idoc type.
Please let me know the issue.
I am processing old IDOC (created from non sap system) through BD87 and using custom function module. I called IDOC_INBOUND_ASYNCHRONOUS in custom function module.
Chandra

Hello,
Aren't you getting any error messages ? You may check by creating watch points on the message id and / or number .
Thanks

Can I create new IDOC segmemnt in user exit( edidd structure ) forcefully ?

RFFOEDI1 is the standard driver program which call the below user exit zxf08u06...
Am programing user exit ZXF08U06...
In user exit zxf08u06, actually edidd structue contains all the segments...
In user exit zxf08u06, I am reading each segment which are in edidd structure, pulling required data from database and passing this data into this segment, so that this data appears in the IDOC's segments (we02).
Now I need to create one new segment which is not there in edidd structure.
Still I inserted this new segment and updated data. This new is coming in IDOC out put But IDOC was crested with error . Am I not supposed to create new segment whcih was not there in edidd structure forcefully ?
MUCH THANKS IN ADVENCE.

Hi
Go thru the bellow links
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400365
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Thanks
Sunil

Create a new line in the xml-header structure.

Hi,
Can any one tell me how to create a new line in the xml-header structure.
I am doing a IDOC-XI-HTTP scenario.
Actually my mapping create this file:
<b><?xml version="1.0" encoding="utf-8"?>
<ORDERS05>
<IDOC BEGIN="1">
    <EDI_DC40 SEGMENT="1"> </b>
The result must look like this.
<b><?xml version="1.0" encoding="utf-8"?>
<ORDERS05>
<IDOC BEGIN="1">
    <EDI_DC40 SEGMENT="1"> </b>
Thanks and Regards,
Eren

Hi,
thanks for you quick answer.
I found a xsl script.
It works fine.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" indent="yes"/>
   <xsl:template match="*">
      <xsl:param name="depth">0</xsl:param>
      
      <xsl:if test="$depth > 0">
         <xsl:text>    </xsl:text>
      </xsl:if>
      <xsl:text>
</xsl:text>
      <xsl:element name="{name(.)}">
         <xsl:for-each select="@*">
            <xsl:attribute name="{name(.)}"><xsl:value-of select="."/></xsl:attribute>
         </xsl:for-each>
         <xsl:apply-templates>
            <xsl:with-param name="depth" select="$depth + 1"/>
         </xsl:apply-templates>
      </xsl:element>
   </xsl:template>
</xsl:stylesheet>
Best regards
Eren

How to create a simple idoc in practice? can you provide an example?

how to create a simple idoc in practice? can you provide an example with full source code?

Try with the follwoing steps
Sending System(Outbound ALE Process)
Tcode SALE ³ for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ¡V Create Model View
Tcode BD82 ¡V Generate partner Profiles & Create Ports
Tcode BD64 ¡V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ³ for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ¡V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ¡V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 ¡V Send Material Data
Tcode WE05 ¡V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Thanks & regards
Sreenivas
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Take a look at this guide.
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.allsaplinks.com/idoc_sample.html
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
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
Create The Extension Segment
Transaction: WE31
The first step in extending an IDoc is to create the new segments that will go into that IDoc. There are some rules that you need to follow when creating the segments:
- The name of each segment type must start with Z1
- For each field in the segment you need to define a field name and a
data element.
- The data element for the segment structure must be of data type CHAR.
How to create new segments:
Run the segment maintenance transaction WE31.
Type your new segment name, and click on Create.
Define the fields of your segment:
Field name
Data Element for the field (from the ABAP dictionary).
Do not change the Export length!
Save the segment
Run Segment -->Check to check the segment for consistency.
Release the segment for transport. Select Edit -->Set Release. Note that the Release column now has a check mark.
Create the Extension IDoc Type
Transaction: WE30
After you create the segments to be added to the extension type, you can create the extension type itself. Execute transaction WE30, enter the extension name, select Extension type, and click Create. You now have three options:
Create new type: Does not refer to other extension types
Create copy: Copies info from an extension type that already exists
Create successor: Extends an extension type from a previous release
of R/3. You can only have one version of an extension type for
each release.
Enter the Basic IDoc type that this extension type will extend.
The screen now shows the structure of the IDoc type you used as
a reference.
Position the cursor on one of the segments and click Create. This will insert an extension segment as a child of the selected segment.
NOTE: A segment cannot appear more than once in an IDoc type! You must control the use of duplicate segments with the segment attributes (the next screen).
The segment attribute screen appears. Enter the information and save.
Extension segments should not be mandatory (for future upgrades), and will need to have minimum and maximum number of instances defined. This answers the question, for each instance of the parent segment, how many instances of the child segment may we have?
You can press the Segment Editor pushbutton to view or change the segment definition.
Create the new Message Type
You can only use an extension IDoc type by assigning it to a message type. You can create a new message type for this.
First the message type itself needs to be created.
Transaction: WE81
Create a new entry and save. Use SAP established customer naming conventions (good form is to start with a Z and retain the rest of the related SAP message type, so, for example, MATMAS becomes ZMATMAS).
After creating the message type, associate it with the corresponding Basic IDoc Type and Extension Type. This relationship is used when IDocs are sent to or received from a partner to determine what segments are valid and what the hierarchy for those segments is.
Transaction: WE82
Create a new entry and enter the Message type, Basic IDoc type, Extension type, and Release, and save your data. Note: the release assignment is not valid for prior SAP releases.
One message type can be associated with many basic IDoc types; however, you need a one-to-one relationship for distribution via ALE.
regards,
srinivas
*reward for useful answers*</b>

Not able to Create a new Remote Monitoring entry in SolMan 7.0 - RZ21

Hi expert,
I am trying to configure Interface Monitoring on Solution Manager system using BPM concept.
For testing purpose i will be monitoring IDocs from Solution Manager CUA system (which is other client in SolMan landscape) to other Satellite system.
As per the configuration part there should be System entry in the Monitoring Technical Topology, that is in RZ21 -->Topology --> System Overview.
For my system its not there, when i press create a new entry in above menu, it gives me new screen where i enter all the details.
Such as System ID, message server, client, CSMREG user details etc.
After saving the details it gives message as "Inserted successfully in secure storage" with no error message on error screen area.
However when i go back in the RZ21 -->Topology --> System Overview my system does not reflect there, even after refresh.
I am not sure if i am missing anything. please help.
Thanks.

Hi Gagan deep,
Thanks a lot for your inputs.
I have some confusion here, where can i check whether latest CCMS agent is installed or not?
Also if its not installed what steps i need to follow to acive the same?
Thanks again!

Create a new Business Partner with LSMW

Hello,
We want to create a new BP using LSMW. We chose IDoc basic type CRMXIF_PARTNER_SAVE_M03. We want to create it with internal number assignment (we don't have BP ID or BP GUID). Unfortunatelly, when we leave PARTNER_NO and PARTNER_GUID fields empty, we get an error message that we should supply at least BP ID or BP GUID. So what values should we enter in order to create a BP with internal number assignment?
Thanks in advance,
Sergey Kozyrev

Hello Sam,
We don't want to enter any IDENTIFICATIONUMBER because we don't want to see it after in the identification table for the created BP that is presented in the user WebUI. We only want to create a BP with internal number assignment and have an ability to enter all BP data. If it is not possible with IDocs, maybe there is some FM that can perform it?
Thanks in advance,
Sergey

Create PO using Idoc with free goods

Hi guys,
i'am currently working on a projekt i need to create a purchase order containing free goods.
We've already tested the PORDCR/PORDCR1 message and Idoc types PORDCR101/102 with BAPI's
IDOC_INPUT_PORDCR1 - w/ self-defined process code (via we42)
BAPI_IDOC_INPUT1 - w/ standard process code (BAPI)
Nothing worked. Got lots of errors in we05 transaction (mostly status 51)
Important:
We need to give the Idoc the free gods flag so we didnt need to set the net_price.
Thanks for your help guys,
Daniel

Use Order PORDCR102, with your extension say ZPORDCR102.
Create one control table and assign Function module to that table.
Set this new Ztable with all required data like free goods.
Then create new idoc, this new idoc will take message PORDCR102 and extension will pick new table and add free goods flag while creating PO.
Hope this helps

Route of the operator.... while creating mapping for idoc to file

Hi,
Scenario is IDOC to File but certain rules are there while creating a mapping in XI.
This is the description for my scenario :
Within XI this Idoc message needs to be translated into 2 text files:
1 file for the route of the operator
     - Read the idoc data.
     - When reading a new order first get the customer. This will be a new line in the file.
        The customer number will be set into the filed u2018CustomerIDu2019.
     - Then read the items. For every item create a new line in the file. The machine number will be mapped to the field CustomerID
     - The field RouteOrder should get a sequential number. Starting at 001 and updated by 1 for every new line.
Could you please guide me how can i implement this above scenario.
Regards,
Y.Raj

Within XI this Idoc message needs to be translated into 2 text files:
this can be done using multimapping i.e. defining your target messages at mapping tabs in your message mapping.
When reading a new order first get the customer. This will be a new line in the file.
The customer number will be set into the filed u2018CustomerIDu2019.
If there is some condition for identifying new order then you should put condition based on input field.
if customer no doesnot exists in order then RFC lookup can fetch customerno
The field RouteOrder should get a sequential number. Starting at 001 and updated by 1 for every new line.
for this declare varaible in global section and use the same or some builtin function can be used for the same.
Rajesh

Creating a new message in adapter module

Hello,
I already posted the question in this [Thread|Sending Adapter Module to split messages;, but I now create this new topic so you can get points for your answer
Jan from this thread wrote "I know how to send a new message using a new instance of the Module Processor and using ModuleProcessor.process()" and I'm now searching for a code example how to create a new message from within an adapter module. I think it must be something like [this|http://help.sap.com/saphelp_srm40/helpdata/en/8d/6ad6409ff68631e10000000a1550b0/frameset.htm].
Regards
Markus

Hi Sippy,
First of all we need to configure the systems. So that we can transfer data from Outbound system to Inbound system.
Configure an Outbound Process that uses Message Control
Step 1: Create a new Message Type
TCode: We 81
Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
Step 2: link the IDOC type to the Message Type
TCode: We 82
Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
Step 3: Create a new Process Code
TCode: We 41
Path: From the Area menu of EDI, choose Control,Outbound Process COde
Step 4: Create or Change a Partner Profile
TCode: We 41
Path: From the Area menu of EDI, choose IDOC,Partner Profile
Configure an Outbound Process for Stand-Alone Programs.
1. Create a new message type
2. Link the IDOC type to the Message Type
3. Add the message to the ALE Distribution Model(use BD 64)
4. Create or change the Partner Profile
I think this will be helpful for you.
Reward points if useful.
Cheers,
Swamy Kunche

Creating a new IDoc

Similar Messages

Maybe you are looking for