Sales Order IDOC creation using IDOC_INPUT_ORDERS

I am trying to create a Sales order IDOC (Inbound) from a flat file using the FM - IDOC_INPUT_ORDERS .
I am able to create the sales order. But I don't see the idoc getting generated anywhere.
I see the import parameter - DOCUMENT_NUMBER coming blank. Why is the IDOC not getting generated ?
Any tips will be useful ?
Can we create Inbound SAles Order IDOC using 'MASTER_DISTRIBUTE_IDOC' FM ?
THanks.

Hi Shareen Hegde
To create Inbound...idoc
Use the Function Module in you Program : IDOC_INBOUND_WRITE_TO_DB to create the Inbound idoc
Pass the Control record and Data record in FM.....
Use Message type : Orders
IDoc type : Orders01 or 02 or 03 or 04 or 05 .... which ever suite for your requirement....
Process Code : ORDE
When ever your custom program for creating the inbound sales order with runs .....
it call the internally FM IDOC_INPUT_ORDERS to create the Sales order...
or
If you are getting the inbound idoc from subsystem .....then check you partner profile ,Message type ed and Process code is correct or not....
I hope this resolves your issuse..
Ramesh

Similar Messages

Initiate Sales Order IDOC creation

I configured Message Control for sending IDOC on Sales Orders create / change in VA01 / VA02. It works.
IDOC type: ORDERS05
FM: IDOC_OUTPUT_ORDRSP
2 questions:
1) How can i send the same IDOC from my program whenever i want. In other words - initiate Sales Order IDOC creation.
2) Will be IDOC sent when Sales Order status is changed:
- Delivery in VL01N
- Sales Order is canceled

Hi,
Please clarify if you want to send all the sales order by a report or sales order for specified condition. If you are able to find a standard program that populates ORDERS05 idoc type and send it is well and good. other wise you need to fill these segments by custom select statement and send it.
Thanks & Regards
Ramachandran Babu

Sales order IDOC process Using FM J_4A_IDOC_INPUT_ORDERS

Hi ABAP gurus,
i am working on Sales order creation using IDOC .
while i am Filling idoc i am filling reference document number and
item number .(VGBEL and VGPOS). but when i process idoc i am not getting reference document number at item level. here we processed idoc using FM J_4A_IDOC_INPUT_ORDERS.
Please suggest me which segment do i neeed to fill for getting reference document number at item level .right now i am using E1j3p02 segment.
or do i need to implement user exit for this.
thanks,
Neo.

Hi Shareen Hegde
To create Inbound...idoc
Use the Function Module in you Program : IDOC_INBOUND_WRITE_TO_DB to create the Inbound idoc
Pass the Control record and Data record in FM.....
Use Message type : Orders
IDoc type : Orders01 or 02 or 03 or 04 or 05 .... which ever suite for your requirement....
Process Code : ORDE
When ever your custom program for creating the inbound sales order with runs .....
it call the internally FM IDOC_INPUT_ORDERS to create the Sales order...
or
If you are getting the inbound idoc from subsystem .....then check you partner profile ,Message type ed and Process code is correct or not....
I hope this resolves your issuse..
Ramesh

No batch input data for screen SAPMSSY3 0131 in Sales order IDOC

I am processing Sales order IDOCS in status 64 using RBDAPP01 .Some of them error out to status 51 with the message -
No batch input data for screen SAPMSSY3 0131 .
I know the standard IDOC inbound process tries to simulate the posting in a BDC like process.
Now, I went to we19 and the screen hangs up in a pop up in the partners tab with partner type 'WE' and my shipto (which is actually filled in the IDOC), missing..upon repeatedly hitting enter, it goes thru and an idoc is posted in status 53. But still unable to get through the root of this issue.
Any, insight will help.

Hi,
I think the pop-up is generated through and user-exit for which recording is missing. This is why your idoc stays in status 64...
Handle the screen recording in the user exit IDOC_INPUT_ORDERS
user exit routine
PERFORM customer_function_dynpro.
FORM CUSTOMER_FUNCTION_DYNPRO.
CALL CUSTOMER-FUNCTION '002'
    EXPORTING DXVBAK   = XVBAK
              DVTCOMAG = VTCOMAG
              DLAST_DYNPRO = LAST_DYNPRO
              DXMESCOD = IDOC_CONTRL-MESCOD
    TABLES    DXBDCDATA = BDCDATA
              DXVBAP    = XVBAP
              DXVBEP    = XVBEP
              DYVBEP    = YVBEP
              DXVBADR   = XVBADR
              DYVBADR   = YVBADR
              DXVBPA    = XVBPA
              DXVBUV    = XVBUV
              DIDOC_DATA = IDOC_DATA
              DXKOMV    = XKOMV
              DXVEKP    = XVEKP
              DYVEKP    = YVEKP
    EXCEPTIONS
              USER_ERROR = 01.
Regards,
Krishnakumar

Segment for WBS element in Inbound Sales Order Idoc

Hi gurus,
I am trying to create an inbound idoc for sales order ' VA01'. I need to populate WBS element in the item level under Account Assignment Tab. I am using ORDERS05 basic type. Please help to find which segment to use for WBS element. Waiting for your reply. Please help.
Regards,
Satyajit

Hello,
        As far as I know, there is no Segment / Field definition in ORDERS05 for WBS Element as it is not mandatory information to be filled in order for the Sales Order to be Complete. So, you need to create an Extension of the IDoc Type ORDERS05. For your requirement, here is the Approach I have.
1. Create an extension for IDoc Type ORDERS05 to ZORDER05 with a Custom Segment Z1EDP01 in which you'll have the Custom Field Name VBAP-PS_PSP_PNR which is the WBS Element field in VBAP Table.
2. Now, use the Customer Exit EXIT_SAPLVEDA_001 in the Enhancement VEDA0001 in which you can actually populate the Field WBS Element that would be already available in the Inbound IDoc to store it in a Work Area. As you are aware, you'll need to create a Project in CMOD for the same.
3. Export the same to some MEMORY ID 'XXX'.
4. Come back to the Selection Program for ORDER05 which is IDOC_INPUT_ORDERS in which you'll find the below CASE Statement.
    CASE xaprau.
          WHEN ' '.
            PERFORM call_va01_new_orders USING ok.
          WHEN 'Q'.
Aufruf Transaktion Auftragerfassung VA01 mit Bezug auf Angebot
call transaction Order Entry VA01 with refer to quote number.
            PERFORM call_va01_new_orders_angbt USING ok.
          WHEN 'C'.
Aufruf Transaktion Auftragerfassung VA01 mit Bezug auf Kontrakt
call transaction Order Entry VA01 with refer to contract number
            PERFORM call_va01_new_orders_contk USING ok.
          WHEN 'L'.
5. Now, since our Standard Order Type (VBAK-VBTYP) is 'C',
    we'll have to choose the Subroutine for the 'C' Option.
6. In this Subroutine, there is another Subroutine va01_dynpro_kopf_kaufmann_kde2 which is for populating Custom Dynpro Fields for the Sales Order. So, we need to choose the same Subroutine inside which we have to Create an Enhancement Implementation.
7. In this Enhancement Implementation (Implicit), we have to IMPORT the value of the WBS Element which was exported in the Customer Exit.
8. Check if it is initial. If it is not, then Call the Perform as below.
     IF NOT WA_Z1EDP01 IS INITIAL. "Checking if the Segment
                                                       " is Empty
   PERFORM DYNPRO_SETZEN USING 'COBL-PS_POSID' WA_Z1EDP01-ZZWBSELEMENT.
ENDIF.
9. Since the Sales Orders are posting using BDC here, by calling the above Subroutine DYNPRO_xxx, we are appending our Custom Segment / Field value to the BDC_DATA table.
10. In Step 8, I've given the Notation for Work Area. It will also be applicable when there are multiple Line Items. All you have to do is to EXPORT an Internal Table instead of Work Area and use the same here for each Line Item.
11. I've given you above procedure because I've worked on similar requirement in which I had to populate the Special Processing Indicator instead of WBS Element.
Hope it would be helpful for you.
Thanks and Regards,
Venkat Phani Prasad Konduri

Creating inbound Sales Orders IDOC within SAP

Hi,
I receive a flat file containing sales order information. I would like to create inbound Sales Order IDOCs from this flat file. I know I can use BAPI_SALESORDER_CREATEFROMDAT2 to create sales orders however I would like to retain the benefits of IDOCs e.g. error retention and re-processing.
There are a number of functions MASTERIDOC_CREATE* to create various IDOCs but I can't seem to find one for message type ORDERS. I know I can create a 'Z' version but would like to avoid that as much as possible as development budget is tight.
Any help would be greatly appreciated in the form of reward points.
Thanks and regards,
Liam

Hi,
Can u tell me the steps to create a sales order using idoc, i've created a bapi but thats a temprory use. I wanted to created a sales order automatically when a purchase order is saved.
Please let me know if u can help me, i wanted to do it using idoc
Regards
Sanju

Sales order delivery creation in background

Hi,
my requirement is i want to create create sales order delivery creation in background . how to do it.
any sample code plz .
with regards
sri.

hi,
use this function module.
WS_DELIVERY_UPDATE_TO_CREATE

Sales Order iDoc from SAP SCM 7.0

Hi Experts
I have two question fro you guys.
1. Can we generate VMI sales order idoc from SAP SCM 7.0? I know is can generate xml message. If we can generate idoc for VMI sales order from SAP SCM , please give me some direction or path to explore.
2. Can I use idoc to to create to VMI sales order in ECC skiping CIF. But the changes in ECC to these order should use the CIF to update the VMI orders in SAP SCM.
Please share your experience on this.

Hi,
Did you set up this scenario? I want something similar, but I want an ERP order to be created. Do you know if that is possible? Do you have som tips?
regards Camilla

User exits for route determination in Sales order & Deliver creation

Hi Gurus,
I need to do some change in the route determination for both sales order & Delivery creation.
Can anyone suggest me which user exit I have to use.
Appropriate answers will be awarded.

Hi,
You can use the following exit for route determination - EXIT_SAPL0VRF_001.
The FM documentation is below. Check the functionality:
"The customer exit can be used for customer-specific route determination or to modify the inbound data for the company's own route determination.
The following data is transferred to support customer-specific route determination:
I_VBAK current order header (for route determination in sales order)
I_VBKD order business data (for route determination in sales order)
I_VBAP current order item (for route determination in sales order)
I_VBPA current sales partner
I_LIKP current delivery header (for route determination in delivery)
The following data can be modified and transferred back to the standard route determination or used for a specific route determination:
C_ALAND Country of departure
C_AZONE Departure zone
C_LLAND Destination country
C_LZONE Receiving zone
C_VSBED Shipping condition
C_TRAGR Transportation group
C_GRULG Weight group
C_FLAG_GEN_VT Flag: Route determination with generic shipping
requirements/transportation group.
C_FLAG_INCR_GRULG Flag: Increase weight group if no route
If you want to use a standard route determination with different parameters, trigger the exception 'CONTINUE_WITH_STANDARD'.
In the log table C_PROT, the log data from the customer-specific route determination can be transferred back. In this case, the log entries always refer to customer-specific messages. To add a message to the log table, the function module SD_ROUTE_DET_LOG can be used (see below).
If a route is determined in the customer-specific route-determination, it can be transferred back in the E_ROUTE field. If no route was found, the exception 'NO_ROUTE_FOUND' is to be triggered."
Thanks.

How can we remove an unwanted # in sales order texts created using a bapiFM

Hi,
i've written the following code which splits the record fetched from apllication server and moves it into a workarea.
CONSTANTS:c_sep VALUE cl_abap_char_utilities=>horizontal_tab, "for separation
SPLIT wa_tab1-rec1 AT c_sep INTO wa_inf_itm-inf_vbeln
                                       wa_inf_itm-itm_number
                                       wa_inf_itm-material
                                       wa_inf_itm-req_qty
                                       wa_inf_itm-uom
                                       wa_inf_itm-amount_pr00
                                       wa_inf_itm-amount_pi02
                                       wa_inf_itm-amount_mwst
                                       wa_inf_itm-amount_vprs
                                       wa_inf_itm-currency
                                       wa_inf_itm-text.
Here c_sep will have a value '#' instead of 'space' in Flatfile from application server.
The field 'wa_inf_itm-text' though it doesnot contain any value in debugging, when the sales order is created using FM 'BAPI_SALESORDER_CREATE_FROM_DAT2' the item texts are having a # character at the end of the text if it has any text(when checked in va03--sales order item text) or if it doesnot contain any text ,then also # character is seen in texts.
Thanks & Regards,
Prasad Reddy.

hi
use
Replace all occurrence of '#' with space from .......
I think it will solve ur problem.
Rewards with point if helpful.
Regards
Santosh.

Error while creating sales order with ref using SD_SALESDOCUMENT_CREATE

Hi
I am creating sales order with reference using function module SD_SALESDOCUMENT_CREATE , while creating i am getting error
Document doesn't have document category even thougth i am passing document category in header as well as item lavel.
In VBUK table there is no value for VGTYP.
Can you please help me how to resolve it.
Thanks & regards
kiran

Problem resolved by passing REFDOC_CAT in the FM along with SD_DOC_CAT.
Thanks

How to transfer sales order idoc from R/3 to CRM

Hi,
I want to generate the sales order idoc in R/3 (ORDERS) and replicates to CRM through XIF adapter.
The sales documents are not realy existing in R/3. We can only get the information from related biling documents and try to gerenate ORDERS idoc.
The problem is how to map R/3 idoc to CRM idoc(CRMXIF_ORDER_SAVE_M01). The administration console seems can only send the idocs but not receiving them.
Thanks,
Ina

Hello Yina,
Can you please answer the questions? I am a little bit confused.
If you don't have the order in R/3, are you not going to create one when creating the ORDERS IDoc? If yes, then this order will go to CRM automatically if you have the middleware set properly.
If you are NOT creating any order in R/3 during the IDoc step, Why would you want the order in CRM when you don't have it in R/3?
Are you not going to keep the middleware between R/3 and CRM open? If you keep it open, the order from CRM will crossover to R/3 - in which case you could have created the order in R/3 in the first step itself !!!
If you are not keeping the middleware open between R/3 and CRM - I don't know why would you want to keep the orders in CRM, but not in R/3. Is it because of lack of good CRM consultants in the project?
Easwar Ram
http://www.parxlns.com

Error in Sales Order idoc - No appropriate entry found in table ADRT

Hello SAP Gurus,
When I am retriggering a sales order idoc I am getting the following error message.
No appropriate entry found in table ADRT
How can I resolve this issue.
Thanks,
Narayan.

Hello Lakshmipati,
I have checked up the customer master. There was no communication method maintained for any of the customers.
But even then the order idoc is triggered to our XI system.
For the one that failed I have maintained the communication method and retriggered again. It had the same failure message.
Any helpful thoughts is highly appreciated.
Thanks & Regards,
Narayan.

Need code for sales order create report using bapi's

need code for sales order create report using bapi's

Hi,
Go through below link
http://www.saptechies.com/bapi_salesorder_createfromdat2/
<b>Reward points if it helps,</b>
Satish

I Need Sales Order Status Reports using ALV

Hi I Need Sales Order Status Reports using ALV.

HI!
For alv use REUSE_ALV_GRID_DSPLAY function module.
For the given report fetch data from the tables:
VBAK - sales order header
VBAP - sales order details
VBUK - sales order header status
VBUP - sales order items status
Regards
Tamá

Sales Order IDOC creation using IDOC_INPUT_ORDERS

Similar Messages

Maybe you are looking for