Idocs for Purchase RFQ

Hi Friends,
Does anybody knows how to configure, an Outbound Idoc to non SAP application for Purchase Request For Quotation? And after inbound a similar Idocr for update Quotation into SAP using estandar Idocs messages?
Thanks for your help,
Andres.

Hi
Check these links for 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
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.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
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)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Check 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://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
<b>Reward points for useful Answers</b>
Regards
Anji

Similar Messages

Generating idoc for Purchase orders - ORDERS05

Hi,
Can you please let me know how to generate idoc for Purchase orders - ORDERS05-manually, not by activating change pointers.

hi
i believe u wont have this functionality as it is a transcational data and the one way of doing it by configuring output types only.

Creating an IDOC for purchase order

Hello gurus,
I want to generate an IDOC for purchase order.
The Logical System, RFC connection, ports definition is already defined.
In my system i have 800 client as source/sender and 100 client as target/reciever.
On Outbound side-> In Partner profile
I defined-
1. Partner No.- devclnt100
2.Type- US (User)
3. Agent - SAPUSER
In Outbound parameters-
I created message type as Orders.
One thing to note that my partner system is LS i.e. Logical System
Then in Outbound Options-
I mentioned Reciver Port - 800Port
Output Mode- I selected "Transfer Idocs immediately"
& "Do not start subsystem"
In Idoc type-
I gave following information-
Basic Type - Orders05
In Message Control tab i mentioned-
Application - EF
Message Type - NEU
Process Code - ME10
In NACE Transaction Code-
I selected EF Purchase Order as my condition for output control
In that- In output types-
I selecte NEU and double clicked. I checked whether Access to Conditions check box is checked and multiple issuing is checked.
In Dialog structure-Processing routines I checked that -
For Output type - NEU
Application - EF
Processing routines are defined-
medium-Distribution ALE
Program -RSNASTED
Form Routine - ALE_PROCESSING
I think these are the very basic settings that need to be done for creation of Idoc.
Now when i create a PO and then SAVE it an IDOC must be generated.
But when i go to transaction Code WE02. It shows me message "No Idocs genereated".
What is the problem? Where am i going wrong?

Hi Yayati,
Here are all the settings that you need to do. I am not sure which all settings are present so kindly confirm.
Sending side Client800:
1. WE20 - under LS - Outbound parameters - message type = Orders , basic type = Orders05
2. BD64 - message type - sender = client800, receiver = client100, message type = Orders
3. NACE - App = EF - Output Types - Processing Routines - Add medium = A (Distribution (ALE)) , Program = RSNASTED, Routine = ALE_PROCESSING.
4. NACE - App = EF - Output Types - Partner Functions - Add medium = Distribution (ALE), Funct = VN.
5. Name - App = EF - Condition Records - Output type = NEU , Choose ur combination (Mine is DocType/Purc Grp)
Pur.Doc Type = NB (Execute) , Add row Medium = A ,Function = VN and other details u choose.
Receiving side Client100:
1. WE20 - under LS - Inbound parameters - message type : Orders ; Process Code : ORDE
2. BD64 - message type - sender = client800, receiver = client100, message type = Orders
For the PO which you have created, go to the PO in ME23N, click on messages .
There should be a line : Output = NEU, Medium = Distribution (ALE)... etc.
If its present then the configuration was correct.
If it has a yellow triangle means it was not processed.
Regards,
Jovito.
Edited by: dsouzajovito on Dec 30, 2010 10:24 AM

Standard Idoc for Purchase order?

Hi,
Can you please let me know what is the Standard Idoc for Purchase order?
POINTS WILL BE AWARDED

Hi Guest
You can use it, if all your required field are in that Idoc basic type.
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://abapprogramming.blogspot.com/2007/11/abap-idocs-basic-tools.html
Award points for helpful answers

Standard Idoc for Purchase Order Receipt?

Hi Experts,
Is there a standard idoc for Purchase Order Receipt?
Please let me know.
Thanks,
Rakesh.

here we go:
Goods Receipt MIGO IDOC

Idoc for purchasing order

can any1 explain the steps needed to send a purchase order through ALE/IDOCS
pls explain it with reference to PURCHASE ORDER

Hi,
cehck the same...
This method is used for distributing transaction data like purchase order, sales order etc.
In this method the extra transaction code that we use is we41 (outbound process code) and we use this in the message control tab in the partner profiles.
The transaction codes that are required for this method are
We81
We30
We31
We82
We21
We20
Bd64
Nace
Me22n (purchase order), va02 (sales order) etc.
Ex: purchase order.
Message type: ORDERS
Idoc type: ORDERS05
Outbound process code for purchase order: me10
The steps that are to be followed are:
Check for the message type in the transaction in we81.
check for the idoc type in the transaction we30.
check we82 in which the link between message type and idoc type is there.
create the port in we21.
Configure the partner profiles in we20.
Click on the + button outbound parameters and give the message type, receiver port
Idoc type.
Now press on the message control tab, this is the place where u give the outbound process code. The message type in the message control is the output type that is used in the nace transaction.
Create a distribution model in bd64.
Go to purchase order transaction (me22n).and press the messages tab
In the messages tab give the output type and the distribution medium as distribution-ale and then save it.
Reward if helpful.
Regards,
Nagaraj

Incorrect message type in IDOC for Purchase order change

Hi Gurus.
Please advise on below.
We have several purchase orders that are configured to trigger IDOC upon change. But accidentally, someone has deactiveted the automatic proposal of EDI message type for these Purchase orders which resulted to not transmitting purchase order change documents automatically.
As a workaround, we have proposed to create EDI message manually during Purchase order change. But upon checking in tcode WE09, message type is ORDERS which is PO create instead if ORDCHG for purchase order change.
Please kindly advice on why it is behaving like this for purchase orders with EDI message previously deactivated.
Thanks in advance.
Acel.
To simulate.
Create PO. go to messages, select EDI message then deactivate permanently. Save PO. Release PO if needed. Change PO. go to messages, EDI is not automatically proposed. create EDI message mamanually. Save PO. Release PO id needed. check tcode WE09, for PO create, no IDOC since it was deactivated permanently. For PO change, IDOC was triggered but with incorrect message type ORDERS instead of ORDCHG.

Hi Acel,
You will need to check the settings in transaction WE20 - You will be using a Partner Profile to determine the outbound message, either for each vendor or a generic one.
on the outbound parameters, you will need to ensure that ORDCHG is set up as a message type. If not, add it, ensuring that you use the message ORDCHG, the basic type (or extension) that you are using, usually ORDERS05 and make sure that in message control, you have process code ME02 set up. This should enable the correct message type to be determined.
Regards,
Rob

Problem in triggerring EDI idoc for Purchase order..

Hi experts,
I am trying to create an outbound EDI IDOC for a PO.
I have configured the partner profile in partner type LI with message type ORDERS in outbound parameters. I have created a new output type ZEDI for EDI, and entered in a message control, as application EF, message type ZEDI and process code ME10.
But when i go to the me23n and goto--> messages, but when i click F4 for output type i am not able to see the new output type ZEDI i have created.
And if i also enter NEU with medium EDI, and Partner function VN, and partner 3000(where i configured the parnter profiles), its giving an error as, "maintain outgoing EDI-connection data for partner 3000".
Kindly help me out. please experts reply me..
Nithin

Hi
<b>In the transaction NACE</b>
you need to maintain the necessary 'Z' output type, in your case.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Reg idoc for purchase order

Dear Friends,
I am trying to transfer data of purhcase order (ME21) (with header and item details) from one client to another client.
I am using idoc ORDERS05 for updating the data.
But i am unable to map the fields of the ME21 to the fields of segments of the idoc ORDERS05.
Note: I am using these fields of me21.
*header details
    ekko-ebeln.                             "Purchasing document
    ekko-bukrs.                             "company code
    ekko-bsart.                             " Purchasing Document Type
    ekko-ekgrp.                             " Purchasing Group
    ekko-ekorg .                             " Purchasing Organization
    ekko-lifnr.                              " Vendor Account Number
    ekko-aedat.                            "date on Which Record Was Created
    ekko-pincr.                            "Item Number Interval
    ekko-spras.                            "language
    ekko-zterm.                             "Terms of Payment Key
    ekko-waers.                              "Currency Key
*item fields
    ekpo-ebelp.                             "Item Number of Purchasing Document
    ekpo-ematn.                            " Material Number
    ekpo-txz01.                            " Long Material Number for MATERIAL Field
    ekpo-werks.                          "Plant
    ekpo-lgort.                           " Storage Location
    ekpo-matkl.                          " Material Group
    ekpo-menge.                         " Purchase Order Quantity
    ekpo-meins.                           " Purchase Order Unit of Measure
    ekpo-netpr.                         "Currency amount
pls help.
Regards,
Vinod Kumar.

Hi
chek with currect version of Message type,if it's not in message type do customise segement's.
cheers
venu

Idocs for purchase order in SAP to SAP

Hi
I have to send purchase order from a SAP system to a SAP system, creation and modification both.
I found these Idocs:
ORDER in sender SAP
PORDCR for creation in destination SAP
PORDCH for update in destinaton SAP
My problem is that all of three idoc have different segments, so i have to map field by field: is there a different solutions, always using idocs and not BAPI directly?
Thanks lot.
Matteo Vernile.

Hi Matteo,
To send purchase orders you can use next Idocs:
1. Creation -->Idoc type: PORDCR102 Message: PORDCR1 This Idoc is based on BAPI_PO_CREATE1
2 Modification --> Idoc type PORDCH02 Message: PORDCH This Idoc is based on BAPI_PO_CHANGE
Using standard boldSAP message determinationbold you can create these Idocs without create any ABAP program.
If you are not creating the Idoc using the standard Message Determination, you should obtain the data using the bapi BAPI_PO_GETDETAIL.
Reward points if helps.
Regards,
Roger

Issue with ALE configuration for creating the idoc for Purchase orders

Hello,
I am trying to send the purchase order through message type configuration using ALE.
I am using idoc ORDERS05, message ORDERS, Process Code in Partner profile ME10.
In NACE transaction for the Application EF, Output Type NEU the ALE Configuration is done for Program RSNASTED Form ALE_PROCESSING.
I have done ALE distribution using BD64.
Now the problem is that when an order is created or changed in the message output of the PO I am seeing the status as yellow i.e.not processed.
In NAST table, the entry is there but on executing RSNAST00 nothing happens.
Please provide me the pointers to solve the given problem.
Regards,
Mayank

Hi,
Guess it looks like the output is getting proposed but its not getting processed. Check the output type configuration. Check the TIme Settings in the output type configuration.
It is possible to set the Time when the output must be processed. Is it on SAVE or is it set to other settings. If its set to via background job then the background job must be run to process the output types.
Check and let me know if all is fine at the output type configuration.
Cheers
VJ

How can create IDOC for Purchase Requisition

Hi all,
whenever I change the Purchase requisition(Tcode-ME22N),IDOC has to be generated automatically.Please help me out.

Hi ravi,
It seems you are talking about the purchase order change.
because ME22N is a transaction for editing the purchase order.Purchase req. is a internal document which we dont send out to any one.
Anyway what is the output type you are using?.
If you use NEU then no need for any changes.
otherwise use NACE transaction and select your output type then mark the 'multiple issuing ' flag.
So whenever there is a change system senses that and proposes the output.
After that you got to make the settings at the partner profile using WE20 transaction.There at the message control parameters level mention the output type and set the change flag.
Entry could be EF ( App.id) NEU (output type) and X (Change flag).
So system generates the IDOC whenever you do the change using ME22n transaction.
Please let me know if you have any issues.
Thank you.
Regards,
karun.M

ALE IDOC for Purchase order to sales order

Hi Friends,
I am sending P.O. from one system to other,using message type ORDERS and basic type ORDERS05 .
On receiving system I am using inbound process code ORDE.
Sending is successful but on receiving side its giving me error, VKORG, VTWEG, SPART cannot be determined for customer 0000000001 .
So please suggest me some solution on this ,,
Proper points will be rewarded to helpful answer.
Thanks,
Brijesh........

Hi brijesh,
I am also working on creating PO to SO . The problem you are getting is one of the problem i have faced . But we can solve this easily.
In your outbound idoc you have 4 fields with E1EDK14.
This segment stores the values for SPART,VTWEG,VKORG .
So in the qualifying fields of this segment 006,007,008 should be there for the above fields respectively and their values in the orgid field.
I have written the coding in outbound side user exit.
MM06E001 in the 11th function module .
so try this it will solve the problem.
Thanks
vamshi

Regarding include long (standard) text in Smartforms for Purchasing RFQ...

Hi,
I have trans code me42 (RFQ).....
For EBELN = 6000000026 i have 2 line items say having 2 material numbers and their quant, units and delivery date etc....
Ok Now I select first line item and then i go to item -
> Texts------>text overview
I get item text and Material PO text. And then I double clik on any one of the text it goes to text editor and then i Go to----> Header.
I get the text id-- A01
textname-- 600000002600010
text object-- EKPO
language-- EN
Now I have all the information other than item text and material Po text.
I just kno it is sumthing related to include text but I dont kno how to display it in layout....
What is the procedure step by step?
First tell how to declare it in smartforms and then in calling program from wer i m goin to display.
Please tell me step by step both in smartforms and calling program.
Also For one line item 'text name' is 600000002600010, text ID is A01A03 and For other line item it is 600000002600020 and text ID is A01 A03.

Just write the code within smartform by using program lines..
pass ur rfq number and item number to form routine.
in the form routine call read_text Function module ,this fm will get the text ..

IDOC for purchase order

Hi,
I created an IDOC using the basic type orders04 , i populated all the required fields and tried to run the idoc through WE20 .The idoc got generated but with an error saying "Purchasing document & does not exist"..I am not able to see which part of the segment this error is getting popped up.Please help me.
Thanks & Regards
Abhishek

Hi Abhishek,
In your header you suggest that you want to create a purchase order using ORDERS04; however this message can't be used to create purchase orders. You should use message PORDCR instead.
In case you do want to create a sales order, you could set a break point in function module IDOC_INPUT_ORDERS at the call of transaction VA01, switch MODE to 'A' and the sales order is created in dialog mode. Perhaps you might then find out what the cause of the error is.
Hope this is of any help.
Regards,
John.

Idocs for Purchase RFQ

Similar Messages

Maybe you are looking for