Create SO from IDOC

Can anybody send me the code for creating SO from IDOC using IDOC_INPUT_ORDERS??
Thanks in Advance.

Hi,
You need to do any coding for creating a sales order using idocs. You just need to make below ALE settings to create a sales order through a idoc.
Steps:
1)create Logical system for source system and target system.
2)assign the logical systems created to the clients as required.
3)Create the RFC destination for the source system and the target system.
4)Create the partner profile using the txn WE20 and
add the message type 'ORDERS' in the inbound parameters tab and mention the process code as 'ORDE' and save it.
5)create the distribution module and mention the sender as ur source syatem and reciever as the reciever system
also select the model and click on add message type icon and mention the message type as 'ORDERS'. and save it.
now if you send the idoc to this system it will create the sales order in the target system. you can test this using txn WE19.
Thanks,
Prasanna

Similar Messages

Create vendor from IDoc

I need to create vendor in a client and the vendor details are available in the same client. So there wont be any inbound idoc coming from anyother system. I need to trigger my inbound idoc in the same system and also create the vendor.
I used function module IDOC_INPUT_CREDITOR. Its creating the vendor, but its not creating the idoc. I think we have to create the idoc first and give the input here. Shoul i manually insert the contents to EDIDC table for creating idoc or any other option is there

c

Create MRO from idoc isu_mr_upload02

Hello Experts ,
I am trying to create the mro from inbound idoc isu_mr_upload02.
Populated the segment E1BPEABLUUPDATE but unable to post the idoc successfully.
Pls suggest on this.
Thanks,
Vishal

Hi Vishal,
Can you please elaborate your query as in what parameters have you passed in the segment?
What is the error you getting after procesing the IDoc? Check status of IDoc in WE02.
For more information on the IDOC ISU_MR_UPLOAD_02 please refer the below link.
http://help.sap.com/erp2005_ehp_02/helpdata/en/30/a9f01a46c0452282c48bb4cff9bbe2/content.htm
Thanks

Create shipment from IDOC

Has anyone ever tried to create a Inbound shipment ( VT01N; containing inbound deliveries) via Idoc? I have tried with message type SHPMNT and SHPADV, and Idoc type SHPMNT03.
I have tried all variations with the segments and still it gives a error message. many time, it says, Delivery 180000xx not found in shipment. Well, i am trying to create a shipment, so how can it be in shipment before

Hey,
have you found a solution for this topic?
This would be very interesting for me!
I try to generate an inbound shipment automatically. But with using SHPADV I only managed to create an outbound shipment.
So far I managed to generate automatically an inbound delivery after creating an outbound shipment manually.
Next step would be to automatically create an inbound shipment to simplify goods receiving.
Propably sombody got a solution and can give me a hint?
Thank you very much in advance!!

Transfer of Results from IDOC to Inspection Lot

Hello experts,
Following scenario:
Inbound IDOC (QCERT) from vendor with inspection results is supposed to populate the inspection lot, which is being created at GR for PO.
QM in procurement is active and QM control key and ceritificate type populated in material master record. We also activated workflow, which is supposed to execute the transfer from IDOC to the inspection lot automatically as soon as inspection lot gets status CROK.
This works only under certain circumstances in the following order:
1. Inbound IDOC received
2. Q-certificate created automatically from IDOC with intial status "2 - Certificate received"
2. GR posting for PO
3. Manual setting of status "5 - Certificate filed and inspected"
4. Inspection lots receives status CROK and the results are being transferred to the inspection lot
This is okay as a start, but not ideal. We would like to have the following behaviour:
1. Automatic setting of status "CROK" for inspection lot in order to transfer the results as soon as certificate and inspection lot are available.
2. If the IDOC is being received after GR for PO, there is no connection in the Q-certificate to the inspection lot, i.e. the transfer of results will never take place, but it should.
Can anybody help and knows, if this is feasible in SAP standard?
Many thanks!
Martin

With IDOC Type Quality01 there is no reference to inspection lot, but in IDOC type Quality02 there is
a inspection lot reference in segment E1EDLIN-E1CCI01, you will have to find out the logic to auto
populate the lot # , please consult developer if its possible
Thanks
DD

Who know how to reach Create SO from PO Output (IDOC)

Hi, experts,
I have met a problem that need create SO from PO output using IDOC, anyone knows how to reach it? please give me detail steps, thanks very much!
we need to create an SO in company code XYZ from the PO output IDOC( Message NEU ) of another company code ABC.
Im trying to create the SO in the same System and same client , but in a Different Company code.
Edited by: zheng michael on Mar 14, 2011 3:55 AM

Hi,
Take help of ABAPer,
In my project I had done this with help of ABAPer, but not on basis of output.
When P.O saved in one company code,system create sales order in another company code.
Kapil

How to create a inbound IDOC from flat file in Application server

HI All
Our requirement is to create the Inbound idocs from a flat file from application server with in R/3
Could any body please let me know the steps required for this.
Thanks
Malli

1. Read the file using OPEN DATASET and read and fill up the segment info and fill the EDIDC header data
and then call function
CALL FUNCTION 'INBOUND_IDOC_PROCESS'
    TABLES
      IDOC_CONTROL       = i_edidc
      IDOC_DATA          = i_edid4.
a®

Help to Create a Generic Material from Idoc

Hi everyone, We have a problem to create a variant from Idoc, our problem is which segments to fill and how to do this?, For create an individual material is ok, we create a material from Idoc Artmas3 without any problem, but when we want to create a variant we had the following error
Message MH197
"No value assignment transferred for the variant-creating characteristic..."
Someone of you had created generic materrials? How do you fill the segments? Which Idoc do you use?,please help us
Regards

Hi,
Initially create a view or identify the table to create generic extractions, remaining process is same in all data bases such as CRM........
GENERIC EXTARCTIONS:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/bi/generic%2bextraction
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf
Generic Delta:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Assign points if these are useful.
Rgs,
I.R.K

Prevent the Output Message when creating PO from inbound IDOC

Hi SAP Gurus,
In my project, I have to create PO from inbound IDOC (PORDCR) with a specific Document Type ('099').
Requirement: These PO should not generate the output message while the others (Doc Type # '099') do.
I have the Z fuction module which call BAPI_PO_CREATE for posting IDOC and it works fine.
In the existing system, there are some set up that trigger the output message type for PO (output NEU) when using ME21 or ME22, as a result my PO created with output message.
Can you please advise if there are some way (User Exit?) that prevent the output message in this scenario (specific PO Type) without touching the current Condition setup?
I'm new in MM and really need help!
Thanks,
Elaine.

Hi Vinod,
I really appreciate your anwer. I'm going to explore this with my functional consultant.
Just like to have more questions:
1. Is it easier if we change the existing condition table instead of creating a new routine?
2. There are two forms for routine 101 (FORM KOBEV_101 and FORM KOBED_101). Can you explain to me why we need 2 here for what purpose of each form.
3. In the debug mode by using WE19 to post inbound IDOC, I change the SY-SUBRC = 4 and PO created without output message. Is it the right direction? Anything else I need to pay attention to?
Thanks again.
Regards,
Elaine.

How to create an inbound Idoc from an inbound IDoc in same client

How to create an inbound Idoc from an inbound IDoc in same client
Idoc will come from XI as an inbound idoc to SAP, now I have to read this inbound Idoc and split it into Several Inbound Idocs and now needs to be posted in the same client.
please let me know the procedure..
Thanks in advance,
Sagar

Hi Sagar,
Develop a cusom Z-Inbound function module, configure the Z-FM to trigger when idoc is recieved from XI. In your Z-Inbound function module split the idoc (Recieved from XI) into respective Idocs and Using MASTER_IDOC_DISTRIBUTE post the IDOCs into the same system.
Thanks & Regards

Create order production from IDOC

Hi!!! how create production order from IDOC INBOUND??... function... BAPI?? thanks...

Hi
welcome to SDN forum
check this BAPi
COXT_BAPI_ORDER_CREATE
Regards
Anji

How to Create PR from exeternal SQL Server through IDOC

Dear all,
I am in trouble while creating PR from exeternal SQL Server through IDOC . although I have created PR from TCODE we19 giving input as well as from function writen below
My scnerio is from external system(Sql) want to send data to sap to create PR return PR No to SQl Server
Not having idea how to do
Basic Type for Idoc : PREQCR01
Message Type : PREQCR
Function Module : BAP_Idoc_Input1
Thanxs in Advance

if you have XI installed,
than it would be easy,
just use JDBC channel->XI->SAP IDOC.
otherwise,
you can export the table from the SQL to CSV file,
and import it with LSMW with IDOC PREQCR01.

Auto Create Outbound Delivery and Shipment from IDoc

Hi Ppl,
Currently, we have a transport company which handles all our transportation of goods to our customer.
We develop a project, phase 1 which we automatically sends sales order in form of IDocs to our transport company and they in turn we send us an excel file on how they have group those sales order into shipment using their own criteria of weight, destination, customer etc.
Now, on our phase 2 of the project, we want the transport company to send us this file in form or IDoc or acceptable file format and which will automatically create outbound deliveries and shipment on how they grouped it.
This should also be able to change deliveries or shipment if the sales order changes.
Please how do we go about this?
Thanks all for your help.

Hello,
As far as I know, you need to have a custom IDoc scenario for this. Here is what you can do.
1. Create a custom IDoc Type to receive Orders.
2. Create a Custom message Type & Custom Process code along with the Custom Posting Program (FM) for this requirement.
3. Perform the validations & process the IDocs by using the WS_DELIVERY_UPDATE & WS_DELIVERY_UPDATE_2 for creating Deliveries & BAPI_SHIPMENT_CREATE FM to create the Shipments.
This being a custom scenario, you'd be required to do some custom development as well in order to meet up with your business needs.
Hiope this was helpful.
Regards,
Venkata Phani Prasad K

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>

Error while creating an outbound idoc using idoc type delvry02

hi,
i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
ERROR:
" SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
MESSAGE NO: AM053
Help would be appreciated.
regards
leo

The message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful.

Create SO from IDOC

Similar Messages

Maybe you are looking for