Creation of sales order via IDoc ORDERS05 - specify a reason of rejectio

Hi,
I want to create a sales order via IDoc (type:ORDERS05), i specify for an E1EDP01 segment a reason of rejection (ABGRU),
The sales order is created succefully by calling the FM IDOC_INPUT_ORDERS but the order quantity of the item where i have specified a reason of rejection is equals to 0.
Is this normal? i want that this will take 3 value either 0?
Could anyone help me?
Thx

Hi,
Thank you for ur answer.
I've followed the procedure that you have explained and the Quantity 3 have been succefully passed to VA01 but is set to zero when i execute the next OK-CODE (=UER2, i think it is llike Enter button ). I simulate the same procedure by creating a sales order on VA01 and i've finally found the problem : at item level, if i enter the Material (MATNR), the order Quantity (KWMENG) and the Reason of rejection (ABGRU), the quantity is set to zero after clicking the enter button ; but if i enter only The material and The quantity followed by enter button, and enter after the Reason of rejection, it works fine, the Quantity doesn't change.
What is the solution that you propose to me?
I've try this one on debugger mode:
The FM which interpret the Idoc create the sales order by CALLING TRANSACTION 'VA01' USING bdcdata....
I've modified the bdcdata to implement the sequence of the steps before (MATNR + QTY <ENTER> ABGRU <ENTER>).
1. Is it possible to code this modification?
2. Is there a way to structure the Idoc for having this sequence in bdcdata?
Thanks in advance!
Narivelo

Similar Messages

Confirm sales order with idoc ORDERS05

Hi everybody.
I´d like to know if it´s possible to confirm a sales orders with idoc ORDERS05 and message type ORDCHG and posting FM IDOC_INPUT_ORDCHG_VMI.
How would I have to fill the idoc data??
Thanks a lot

Hi,
For inbound idoc you can use the message Orders , process code ORDE and the function mdoule IDOC_INPUT_ORDERS to create a sales order.
Regards,
Nagaraj

Cancel a Sales Order via IDOC processing

Hello,
I am trying to cancel an item within a sales order using ORDERS05 (IDOC_INPUT_ORDCHG).
My IDOC contains the following data:
E1EDK01-ACTION = 003 (Changes in one or more items)
E1EDK02-QUALF = 002 (Vendor Order)
E1EDK02-BELNR = SAP Sales Order Number to be updated.
E1EDP01-POSEX = SAP Sales Order Item Number to be deleted (eg. 000010).
E1EDP01-ACTION = 003 (Item cancelled)
E1EDP19-QUALF = 002 (Material number used by vendor)
E1EDP19-IDTNR = SAP Material Number of Item to be deleted
However it does not seem to be working correctly. Instead of removing the item from the sales order - it actually creates a new item.
Has anyone had any experience with successfully cancelling an item using IDOC processing?
Any assistance would be greatly appreciated.
Thanks and Regards,
Corinne

Hi Corinne,
I don't think you'll get back the response you want from SAP. This idoc was originally created to support the EDI scenario where your customer makes a change to their purchase order. The EDI message would be sent to SAP to update the corresponding sales order in your system (after being mapped to an Idoc).
As your customer does not normally not have your sales order item number in their system, they can only send their own purchase order item number. SAP then uses this number to look up the corresponding SAP sales order item number via the VBAP-POSEX field (which in this scenario is originally populated by the Idoc which created the order from the customers original purchase order EDI message).
So, I dont think SAP will change this functionality. They may offer, however, a work around!
What I still think is strange though, is that, having not found a match for your item on the POSEX field, SAP ignores the deletion flag and adds a new item to your order. At the very least you would expect it to just ignore the item (a quick look at the code in 4.7 seems to imply that this is what SAP is trying to do - maybe a change from your version?).
Hope that helps.
Brad

Creation of sales order using IDOC

Hello All,
PO is created in a website,which comes to SAP as a Idoc.Sales order need to be created with this idoc information. We are extending ORDERS05, since we are in need to add z segment as a child segment of E1EDKA1 to hold 3 email addresses.
Could anyone say how to handle these email addresses in SAP and which exit is to be used for the same?
Is that EXIT_SAPLVEDA_001 or EXIT_SAPLVEDA_004.
Thanks in advance.
Meenakshi

Hi,
its EXIT_SAPLVEDA_001.
Regards

Problem creating sales order using IDoc ORDERS05 (Inbound)

Hello Experts,
We are trying to create a sales order using the IDoc ORDERS05 with process code ORDE for creating sales order. I am getting the following error "VKORG, VTWEG, SPART cannot be determined for customer 0000006000 , vendor
Diagnosis
No sales organization, distribution channel or division were sent to the IDOC. This data is necessary if a sales order is to be added automatically. If this data is unavailable, you cannot create a sales order document.
I was not able to find the fields to fill the distribution channel and divison in the Idoc structure. I have filled in Sales organization in E1EDK14 segment as 3000.
I am not able to figure out the cause for the error.
Same data works fine from BAPI_SALESORDER_CREATEFROMDAT2.
Please help.
Thanks,
Suma
Edited by: Suma B on Jun 17, 2008 11:12 AM

Hello Suma
In this case I would recommend to debug the IDoc processing.
Call transaction WE19 and start the inbound processing of your IDoc in debugging mode. The error message will most likely occur in function module IDOC_INPUT_ORDERS.
LOOP AT idoc_contrl.
* SET/GET Parameter und interne Tabellen neu initialisieren
* initialize SET/GET Parameter and internal tables
    PERFORM initialize_organizational_data.
* IDOC-Segmente in die entsprechenden Anwendungsdaten übernehmen
* Move IDOC to internal tables
    PERFORM interpret_idoc_orders.                    "<= check here
* Prüfen ob gewisse Segmente gefüllt sind
* check IDOC-Segments
    PERFORM check_idoc_segments.                 "<= check here
* Prüfen und Ermitteln von Organisationsdaten
* check internal tables and determine organization data
Regards
Uwe

Creation of sales order from idoc; items referencing to different contracts

Hi All,
My requirement is to create sales order from an idoc.
IF a sale order contains multiple items , then the order should be created with contract referenced
-at the So item level, the valid contract found for each material is different
hence am not able to use the following bapis
BAPI_SALESORDER_CREATEFROMDAT2 is not triggering the copy controls.
BAPI_SALESDOCUMENT_COPY i can give only one reference document
Please help
Thanks
Deepa

Hi Deepa,
Following link can help you for creating sales order with reference
http://msdn.microsoft.com/en-us/library/cc185190.aspx
http://www.sap-img.com/fu036.htm
Award points if useful
Thanks,
Ravee..

Problem when setting Reason of Rejection for a sales order using IDOC

Hi All,
I am working on a requirement where i need to put a reason for rejection as 'Item Cancelled' for a sales order via IDOC 'IDOC_INPUT_ORDCHG' in a third party scenerio where the PR is created automatically from the sales order . When the IDOC is run in the foreground I get the information message Subsequent function " 'Purchase requisition from sales document' not possible Item & was rejected "(Message V1579) and the IDOC results in a error when run in the background mode because of the same information message. The message should not appear when a sales order is being processed in the background but still the message is being displayed . Is there any way the message can be suppressed ? Thanks in Advance.
Regards,
Sowmya.

can you send the program how you create a so or po using IDOC, as i've a assignment creating PO using IDOC & then creating a sales order of the PO. and i dont know how to create a IDOC. SO IF you have sample program it would be help full
Thanxs

Creation of Sales Order and Service Contract from Inbound IDOC

Hi Experts,
My requirement is to create a Sales Order as well as a Service Contract from one Inbound IDOC. I am getting the Inbound IDOC from a third Party. The message type is ORDERS and Basic Type is ORDERS02. How ever i am using an extension type IDOC which carries all the required data for Sales Order and Service Contract. My requirement is like, to create a Sales Order first.
I have created a Z FM which is attached to the Process Code and subsequently to the message type. Inside the FM i an calling FM 'IDOC_INPUT_ORDERS' for creation of Sales Order. After that i am changing the IDOC data for the Document Type. I am changing the document type which is responsible for Contract Creation.
Then I am again calling the FM 'IDOC_INPUT_ORDERS' for creation of Contract with the help of IDOC data. But here the Contract is not getting created. It's getting failed during the Batch input session.
I need to solve this problem as soon as possible. Please help me. If there are any other options also please share.
Thanks in Advance.
Regards,
Priyabrata

Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
Regards,
Priyabrata

No alternative unit of measure specified, during creation of sales order

Dear Experts,
when user is creating sales order, User is getting the error message no. MM108 "No alternative unit of measure specified" for particular material.
we have checked the alternative unit of measure it is already maintiained in the material master.
we have checked the OSS note : 117611 - Error message MM108 during goods receipt for order, but we couldn't get exact results for our issue.
can you provide the exact reason and solution to over come this please .
Thanks in advance.
Regards,
Suresh Veerepalli

Dear Experts,
The Base Unit of Measure (L) and Sales unit (PCE) ,The alternative unit of measure is maintianed in the material master as shown below.
X                  AUn               Measuremt unit text           Y                   BUn               Measuremt unit text
1     L     l     <=>     1     L     l
1.121     KG     kg     <=>     1.000     L     l
1     PCE     Piece     <=>     1     L     l
1     BDL     Bundle     <=>     12     L     l
1     PAL     Pallet     <=>     720     L     l
Error is gettting when creation of Sales Order ,Order is standard order.
When we double click on error message the following details are shown.
1.No alternative unit of measure specified
message no:MM108
2.Diagnosis:
   This alternative unit of measure is missing.
3.System response :
   The system cannot carry out conversion
4.Prodedure:
This is due to Program error that should not occur.
Please provide the exact solution on this issuse.
Thanks

ERROR IN CREATING SALES ORDER,USING IDOC TYPE ORDERS05

I am using exit to write my code for creating sales order of IDOC Type ORDERS05 and order type ZDRX.
IF I proceess the Idoc in background each time error message comes
FIELD kuwev-kunnr(ship to party)is not an input field.
but if i run in foreground in debugging mode,sales order is getting created..
please suggest something.

If thats not working..
try BAPI_SALESORDER_CREATEFROMDAT2
If BAPI is not working. try creating a bdc for the same if there's not error on trying from VA01

IDoc and creation of sales order!!

Hi,
I need to create sales order using IDoc and the file will have multiple line items for sales order and it has to be dynamic, so whats the best way to do this?
Regards
Gunjan

Hi
Check for the related IDOC types in EDBAS table and for related Message Types
in table EDMSG. take relavent one for your requirement and use.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
Reward points if useful
Regards
Anji

Reference contract within Sales order supplied by ORDERS05 IDOC

I am creating Distributed sales orders using IDOC of type ORDERS05. The orders are being raised okay upto now, but now I want to perform various checks against a reference contract should one be added to the IDOC. The IDOC segment E1EDK02 with a qualifier of '005' (Customer contract) can be used to supply the reference contract. I'm using one of the supplied BADI's to process segments that are not catered for in the SAP standard code, however, I don't know where to populate the supplied reference contract number within the deep structure CRMXIF_BUSTRANS that is available for this purpose.
Has anyone ever processed a reference contract in this manner ?.
Blue

I have found a table within the deep structure CRMXIF_BUSTRANS called DOC_FLOW which seems to have all the necessary fields, I think. However, it's going to be a lot of trial and error to determine what needs to be populated in this table to successfully create a Preceding doc in the doc flow of the Sales order raised. The preceding document being of type CONSIP/reference contract.
If anyone has ever populated this data I would be most keen to identify the exact fields entered.
Blue

Sales Order Using Idoc

Hello All,
We are creating Sales Order through Idocs : Basic Type - ORDERS05 Message Type - ORDERS
Sales Order is being created but for few Items , Reason for Rejection is set (thts not required in our case).
I am trying to figure out why for some items its happening ?
I tried to check the reason by Processing the Idoc in WE19 but could get through.
Also tried to process the Idoc using FM IDOC_INPUT_ORDERS in Debugging but not able to process further as getting error message : 'Idoc Has Different Status'.
Any input on this would be helpful.
Thanks
Praveen

This problem due to your config in the system, try to create a sales order for the item that posted via Idoc then see same item got rejected.. If yes discuss wtih your funtional guys....

Creation of Sales Order throogh Intercompany STO

Dear SAP Gurus,
I have a question
In the intercompany stock trasnport orders.As per the standard process
i) Creation of STO
ii) Creation of replenishment delievry.
iii) Goods Issue from the supplying plant.
iV) Good receipt at the receiving plant.
Our requirement is to create a sales order through IDOC in place of delivery at the delivering company code.
All the subsequent docuements like delivery and shipment will be based on this newly created sales order.
I want to know primarily that is there anyway of creating a sales order instead of Delievery subsequent to creation of STO.
IF so how can we disable the SAP standrad process ( Std Intercompany STO process) and enable our requirement.
A quick response is highly appreciated.
Regards
Ganesh

Hi,
You can create sales order in the background while creating intercompany purchase order.
By using BAPI BAPI BAPI_SALESORDER_CREATEFROMDAT1.
Ask your technical team to desing.
Regards
Ravi Shankar.

Price conditions on Sales Orders via EDI

Hi,
I need to know if there is a way to bring prices over on the IDOC while posting a sales order via EDI. I have a situation where the price does not have to be determined based on condition records setup within SAP but rather update the price sent on the IDOC itself.
Thanks
MR

Hi,
Let the inbound Idoc have the price field and the price of the material. And keep the price condition type open/manual entry allowed. Once this is done the system will not do it from the condition record and will populate the data that is there in the Idoc.
Hope this helps.
Kind Regards
Chakradhar

Creation of sales order via IDoc ORDERS05 - specify a reason of rejectio

Similar Messages

Maybe you are looking for