READING EDI IDOC'S INBOUND ORDERS

HELLO.
DOES ANYBODY KNOW HOW TO READ EDI INBOUND SALES ORDERS IN
ABAP ?
I WANT TO READ THE IDOC'S WITH A PROGRAM
AND FIND THE MATERIALNUMBER AND THE QUANTITY .
THANKS

Hi,
Check out this document for the details:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/abap/an advanced guide to implementing application link enabling.pdf
regards
Aveek

Similar Messages

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

W to read the idoc in inbound

HI Freinds
              I am new to idocs...I have created (custom)idoc using stand alone program in outbound.....then what are the next steps in inbound....if we have to create process code in inbound side....how to read idocs and post the inbound...pls any body tel me clearly....
Regards
Mani R

Hi mani,
You should follow the following steps 1 by 1.
     WE30 - IDOC type creation
     WE31 - Create segment
     WE81 - Message type creation
     WE82 - Link IDOC type to Message type
     SE37   - Create Inbound Function Module
     BD51 - Maintain entry for Function Module
     WE57 - Maintain
     BD57 - Link Function Module, IDOC type and Message type
     WE42 Create Inbound Process Code
     BD67 - Link Process code to Function Module
     WE20 - Create Partner Profile
     BD64 - Display Distribution Model
     WE02 - IDoc List, Display all Inbound/Outbound IDocs
     WE14 - Outbound Processing of IDocs
     BD20 - Inbound Processing of IDocs
1st Step:   Create a Segment ( WE31)
         Segment is a structure for passing data in IDoc. It actually contains the IDoc data, just like the DDIC table/structure. Segment is created with all the required fields. Then Save it. But, to actually use this Segment, you have to Release the Segment, otherwise u cant use the Segment, by menu, EDIT--> Set Release.
         Now, if you want to do some change to this Segment, u cant, unless & until u Cancel the Release, by Edit--> Cancel Release.
2nd Step:   Create IDOC Type ( WE30 )
        After creating the Segment, now we have to create the IDoc Type. IDOC Type is like an envelop of a letter, which contains the data inside it, & also some more information like address. IDoc type can be Basic Or Extended.
       Basic IDoc Type: Using some SAP existing IDOC type (ex. MATMAS) or Custom IDOC type.
       Extension IDOC Type: When we need some fields extra to an existing IDOC type, then we can extend that Basic Idoc Type by another Segment. This is called Extended idoc type
3rd Step:   Create Message Type (WE81)
     Message Type is like the Postman for sending the Letter.
4th Step:   Attach Message Type to the IDOC Type (WE82)
5th Step:   Create a Function Module (SE37)
       Write the Processing logic in a Function Module.
6th Step:   Mention the IDOC Type, i.e, 0/1/2 (BD51)
7th Step:   Assign the Message Type, IDOC Type & Function Module (WE57)
8th Step:   Create a Custom Process Code (WE42)
9th Step:   Attach the Function Module to the Process Code (BD67)
10th Step: Execute Inbound IDOC s (WE19)
Example Function Module: IDOC_INPUT_ORDERS (Standard FM to create Sales Order).
Reward is helpful,
Regards,
Tanmay

EDI / Idoc DESADV Inbound Delivery

Hello,
we send IDocs (DELVRY03,DESADV) as shipping notifications to another R/3 system. The inbound deliveries in the receiving system, generated automatically, are also containing the handling units as delivery positions, which are specified in the IDOC.
How can we prevent this, so that only the actual delivery positions are listed in the inbound delivery? Customizing?
Thanks you in advance.

Hello Mario,
I assume that you have plant and item category filled in your HUs. In this case a delivery item is generated although the corresponding flag at the item category is switched off (this is the 'old' logic of item generation).
Therefore if you want to prevent the item generation you could prevent the determination of an item category (see trx. 0184, entries for EL, PACK).
If you need a more detailed control of the item generation e.g. only for some special packing materials, you might also use the 'ItemRequirement' at the delivery type (in standard 202), which specifies if an item without reference can be added to an delivery (can be maintained by using transaction VOFM - Copy requirements - Delivery).
Best regards,
Ulrich

Changing IDOC Control Record for EDI inbound Orders Creatiion

Hi,
When I try to process the Inbound orders Idocs file through the GENTRAN EDI System.IDOC's were errored out, because of the Partner function was not defined for the Customer ( Legacy ) ( Type KU ) in the SAP.
Is there any user exit/badi/Configuration to change the Legacy Partner(Customer) to the SAP Partner(Customer) mapping and update the IDOC Control record with the SAP Partner. I am calling EDI_DATA_INCOMING Function module and IDOC_INPUT_ORDERS.IDOCs errored out with Message EO-332 ( Partner function not defined ).
Advance Thanks,
Balaji.

It's been a long time since I have done any IDOC processing.
Go to SE37 and enter the function module IDOC_INPUT_ORDERS. Display the source code. Search for "CALL CUSTOMER". You should see several "CALL CUSTOMER-FUNCTION" lines. These are enhancements where you can manipulate the IDOC data. If you locate the correct one (where the data is read from the IDOC but not yet validated), you should be able to map the partner function value. Double-clicking on the number in quotes will bring you to an "EXIT_" function module. A "ZX" INCLUDE program is referenced. If you haven't used the exit yet, double-clicking on the ZX INCLUDE will create it. The values passed into the function module are available in the INCLUDE.
Ideally, you should create a project in transaction CMOD that references the chosen enhancement. This way you can activate/deactivate without commenting/uncommenting the code in the INCLUDE.

How to delete E1EDP19 002 segment frm the inbound ORDERS IDoc?

Hi ABAP/EDI experts,
I am implementing an User exit related to inbound Sales order EXIT_SAPLVEDA_001.
Most of the time my IDocs contain the below segments.
E1EDP19 001 (QUALF = '001')
E1EDP19 002 (QUALF = '002')
Sometimes, IDoc contain only E1EDP19 001 (QUALF = '001') segment.
My problem is whenever i have two E1EDP19 segments, i want to delete the 1st E1EDP19 segment and retain the second E1EDP19 segment.
Can anyone tell me the pseudocode for deleting the 1st E1EDP19 segment from the inbound orders IDoc.
Am i using the correct user exit??
Thanks,
Creasy Matt
Edited by: Creasy Matthew on Jan 22, 2009 12:56 AM

Hi Matt,
You can loop on idoc_data internal table. This table will be having all the data and the segments.
data: l_count type i value 0,
l_tabix type sy-tabix.
LOOP AT idoc_data WHERE docnum = idoc_contrl-docnum.
CASE idoc_data-segnam.
WHEN e1edp19.
l_tabix = sy-tabix.
l_count = l_count + 1.
if l_count = 2.
l_tabix = l_tabix -1.
delete idoc_data index l_tabix.
endif.
ENDCASE.
ENDLOOP.
I hope this will work.
Please let me know if any issues.

Idoc - for inbound delivery order confirmation

Hi,
Can some body give me the idoc for Inbound SO Delivery Order Confirmation and if any BAPI method is there to create Delivery order confirmation.
With Regards
Vasu

Hi Vasu,
Below is the link to find out the IDOC name for ur Inbound IDOC scnario
http://help.sap.com/bp_bpmv130/Documentation/K17_BPP_EN_US.doc
Hope this willl help you.
Reward if helpful.

How to Send Purchase Order through EDI/IDOC.

Hi Experts,
We are using SAP ECC.5. And intending to send the Purchase Order to Supplier through EDI/IDOC and Receive the Inbound Acknowledgement.
Appreciate, if you could help me, the required Configuration details for outbound and inbound (PO & Acknowledgement).
Reg
Kumar

Hi Kiran
Many thanks for the response. It is true that by changing the message type to EDI can generate idoc. What is not clear is any other config we need to do interms of Message generation, Resubmitting failed IDOC etc..
Out requirement is that we would generate the IDOC for New and changed docs and send to external EDI converter.
Inbound, receive the IDoc and post the acknowledgement.
Appreciate, if you could forward any document link which can explain the details.
Reg
Kumar

EDI IDOC General Flow of Inbound to Outbound

Anyone guide me the step by step process for creating an inbound IDoc of purchase order to Outboud IDoc of sending order confirmation back to system? The whole flow including EDI and IDOC from start to finish..
Also it would be helpful if someone give me where to get IDOC list and EDI ..no's

for this you need to write a program .
once you get the data form file to Internal table. then
pass your internal table data to idoc control and idoc dta
like pass all segemnts data then pass all segments data to this FM
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
      EXPORTING
        master_idoc_control            = wa_edidc
      TABLES
        communication_idoc_control     = gt_edidc
        master_idoc_data               = gt_edidd

How to place a delivery block at line item level from Inbound ORDERS IDoc?

Hi EDI/ABAP Experts,
Can anyone please tell me how to place a delivery block at line item level from Inbound ORDERS IDoc?
I tried using exit "EXIT_SAPLVEDA_001'. But there is no LIFSP field in either of XVBEP and YVBEP structures.
Can you guys throw some light. How to place a delivery block @ line item level on sales order from Inbound ORDERS IDoc.
Thanks,
Matt .

Look into the Include: LVEDAF5A that is the only place where this exit is hit... double click on the Structures and look which structure has billling block field.. and use that..
FORM CUSTOMER_FUNCTION_IDOC USING IDOC_DATA.
CALL CUSTOMER-FUNCTION '001'
    EXPORTING SEGMENT = IDOC_DATA
              DVTCOMAG = VTCOMAG
              DXMESCOD = IDOC_CONTRL-MESCOD
              CONTRL   = IDOC_CONTRL
    TABLES    DXBDCDATA = BDCDATA
              DXVBAP    = XVBAP
              DXVBEP    = XVBEP
              DYVBEP    = YVBEP
              DXVBADR   = XVBADR
              DYVBADR   = YVBADR
              DXVBPA    = XVBPA
              DXVBUV    = XVBUV
              DD_FLAG_P = D_FLAG_P
              DXKOMV    = XKOMV
              DXVEKP    = XVEKP
              DYVEKP    = YVEKP
    CHANGING DXVBAK   = XVBAK
              DD_FLAG_K = D_FLAG_K
    EXCEPTIONS
              USER_ERROR = 01.
If you are in ECC6.0 you can also use Enhancement point : INTERPRET_IDOC_ORDERS_01 SPOTS ES_SAPLVEDA. in include: LVEDAF2U

Find status of a sales order created using EDI IDOC

Hello everyone,
   I have IDOC created for incoming sales order using FM 'IDOC_INPUT_ORDERS'.
When a sales order is created manually iva VA01, it prevents the order from being saved when a specific error is hit unless user resolved it first.   However, when the order is created via EDI IDOC, the error is hit and it cannot be created. In the sapmv45a program, i will to say that if it is an EDI IDoc transacion for the order, let it bypass the error and create the order.
     Can anyone pls tell me how to check the status of a sales order being created using EDI IDOC ?
Sy-batch does not work.
Thank you in advance.
Joyce

Joyce,
If you pay attention the code in FM it is exporting value of da_edi_sign to memory id "SD_EDI_ACTIVE" stored in constant "da_memory_id". ('CONSTANTS: da_memory_id(13) VALUE 'SD_EDI_ACTIVE'.)
In your program you have two you have two options.
1. Declare a constant as in the FM and use that as mentioned below:
CONSTANTS: da_memory_id(13) VALUE 'SD_EDI_ACTIVE'.
IMPORT v_memid FROM MEMORY ID da_memory_id.
2. Hardcode memory id as below:
IMPORT v_memid FROM MEMORY ID 'SD_EDI_ACTIVE'.
Hope this resolves your problem.
Gajendra

IDoc Receiver, Error in we02 - EDI: Partner profile inbound not available

Hi All,
I have a problem when creating a receiver IDoc from XI to R/3.
I have successfully tested the IDoc when populating the receiver information from the payload. However I want this information to be populated automatically based on the logical systems.
When I do this I get the following error in the IDoc in R/3:
EDI: Partner profile inbound not available
In the control record the sender information is all correct but in the recipient information the partner Number with type LS is populated, but port is not populated.
I have done the following steps.
     the sender is a Business Service so I have created a logical system directly adapter-specific identifiers in the sender service in the integration directory.
     In the receiver business system I have imported the logical system into the adapter-specific identifiers in the ID from that specified in the SLD.
     In the receiving R/3 system using SALE/BD54 I have created a logical system for the source system.
     In the receiving R/3 system using we20 I have created a partner profile of type LS with the same name as the source logical system.
     IN PI/XI system in transaction IDX1 Ive created a port (SAP<SID> where <SID> is the system ID of the receiving R/3 system) and the client of the R/3 system, and the RFC destination of that system (<SID>CLNT<clnt>, as specified in SM59).
     In the IDOC Adapter (receiver) I have entered the RFC destination and port matching those created above. All checkboxes are UN-checked eg. take sender from payload, take receiver from payload, Apply control record values from payload, etc. are all NOT checked.
I think that Ive done everything correctly, but I get the error in we02 in R/3: EDI: Partner profile inbound not available.
Any help will be greatly appreciated (and rewarded, obviously).
Thanks,
Matt.

HI Matt,
Can you please copy paste the exact error message....In your error message it will show you Exact partner Number / Logical System name and other parameters...just compared if you have all parameters set in your partner profile comparing to error message...
If you can giev screen shot of both..then probably would be easy to point out error.
Hope this will help.
Nilesh

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56 with message "EDI: Sender port in control record is invalid".
But if I reprocess the same idoc without doing any changes using RBDINPUT and select radio button to processs idocs for status 56, then it gets successfully posted.
So not getting why this stucks for the first time.
Thanks in Advance..........

i fixed this my self

How to Identify an whether an Sales order is created through EDI Idoc

Hi all,
By seeing an Sales Order, How to identify whether the sales order is created through EDI Idoc or by other source.
Thanks in advance
Regards
Chakri

Hello Chakri,
As far as I know, for EDI orders a separate order type is created. So, they use to that create the order with an Idoc.
But, remember you can use other order types as well.
Thanks,
Babu Kilari

Inbound IDOC for sales orders not posting the configuration data

Hi all,
I am facing a problem in posting the inbound IDOC (message type ORDERS). The configuration data maintained in the parent segment E1CUCFG and in the segment E1CUVAL is not getting posted though i am passing the data in these segments which is 100% correct.
Can any one solve this problem

Hi Ravi,
Please check the two segments are active. You can do that in BD53.
In BD53 enter message type, and make the segments active.
If segments are active, it appears in white colour.
After this post the IDoc and check with segments.
If its useful, award points pls..
Regards,
Bharadwaj

READING EDI IDOC'S INBOUND ORDERS

Similar Messages

Maybe you are looking for