Segments E1EDK04 and E1EDK05 in IDOC ORDERS05 for PO's

Hi all,
I am using program RSNASTED and form ALE_PROCESSING to generate IDOC ORDERS05 for purchase orders. This works fine but, eventhough the purchase orders contain tax conditions (NAVS) and several header discounts (e.g. RA01), the relevant segments, E1EDK04 and E1EDK05, are not included in my IDOC.
Anyone have an idea how to include these segments?
Thanks and regards, Patrick

Michal_Krawczyk_PIXI wrote:
Hi,
>
> if your SAP version is <4.6A then you need to do it manually
> if not then it should work automatically
>
> Regards,
> Michal Krawczyk
Michal, Sorry it is not working as expected.

Similar Messages

Idoc ORDERS05 for PO Outbound for the Output type ZSUS.

I have a standard Idoc ORDERS05 for the PO.
I have Extended this Idoc and Created a Z- Segment below E1EDKA1 which is ZE1EDKA1.
There are Four Fields in it. i.e. ZZFNAME, ZZLMAE, ZZEMAIL & ZZADDRESS.
When I create the PO using ME21N OR Change using ME22N and use the MEssage type ZSUS which is Configured in the NACE T-Code.
The Idoc Just does not get triggered . I tried to do the same through the test tool. WE19 but yet the Idocs gets Created but the Z-segment does not get populted nor is seen.
I have writtem my code in the Exit 'EXIT_SAPLEINM_002' and have poulated the above mentioned four fields.
But the Idocs just does not reach the user Exit and hence these four fields do not get populated.
I have done the neccessary configuration in WE82 and also in WE57.
Can u please provide me with the Solution.
Regards,
Deepak.

Hi,
Use table NAST

Segment E1EDP20 is missing in IDOC ORDERS05

Hi All,
   EDI Message Type:     ORDRSP
   Basic IDOC type:         ORDERS05
   Function Module:     IDOC_OUTPUT_ORDERS
   IDOC extraction function module: IDOC_OUTPUT_ORDRSP
   While saving the sales order in back end the basic IDOC ORDERS05 is triggering . Segment E1EDP20 is missing.
Please any one explain the above two function module. when it will trigger.
Thanks in advance.
SN

Hi,
Condition records needs to be maintained for the line items in the sales order. Only then E1EDP05 will be populated.
Kindly check for the condition records.
Regards,
Prasana.

Segments E1BPACGL09 and E1BPACTX09 in Idoc type ACC_DOCUMENT03

Hi,
Is it mandatory to use E1BPACGL09 and E1BPACTX09 as the same time for idoc type ACC_DOCUMENT03 and message type ACC_DOCUMENT ?
If we use both the segment at the same time then at the time of posting this idoc through BAPI_ACC_DOCUMENT_POST, this idoc ending up with the error message "FI/CO interface: Line item entered several times".
On further debug i found this error message comes if we use both the segments.
In segment E1BPACGL09 we have value for fields
ITEMNO_ACC
GL_ACCOUNT
TAX_CODE
COSTCENTER
ORDERID
DE_CRE_IND
In segment E1BPACTX09 we have value for fields
ITEMNO_ACC
ACCT_KEY
TAX_CODE.
Thanks,
Asit Purbey.

Hi
I see that you have problems with fields related with taxes. So, check if SAP Note 367175 - No tax calculation function in FI/CO BAPIs is relevant.
I hope this helps you
Regards
Eduardo

ORDCHG - IDOC - ORDERS05 Issue IMP

Hello,
we have configured ORDERS- IDOC - ORDERS05 for ouput type ZSPO. User is going to trigger output manuallly in every case.
If PO is changed still same output will trigger. Till this everything works fine.
Now suppose one item is marked for deletion and output is triggered manually this item does not come in IDOC itself. And i want to send this with deletion indicator.
How can I configure this? I tried adding ORDCHG - IDOC - ORDERS05 with same output type but still ORDERS IDoc gets triggred.
Please suggets.......!!
Thanks

For orders change there is a different process code - ME11 for 'ORDCHG' and ME10 for 'ORDERS'.
In case of changes make sure that in your partner profile setup (WE20) also the correct process code is assigned.
Regards,
Dominik Modrzejewski

Error in IDOC ststus , for interface IDOC to File

Hi All,
iI am doing IDOC to file interface , in which i am using IDOC Orders05, we are using the same IDOC for other interface to connect with DOTNET connectors , when i trigger the IDOC ORDERS05 for my interface when i check the ststus , in which it is pointing the to partner No and Port to that dontnet, not to my Iterface for SAP XI , anyone there to help me in this isssue
Thanking you
Sridhar

Hello,
While sending Idoc you will be providing the Port which in turn needs RFC Destination and this is one which takes the document to External system configured in RFC.
If you need to send the idoc to External Systems other than R/3 then you need to use T type connection which uses JCO for estblishing session. if it is R/3 then requires logon credentails and type 3 for configuring RFC.
HTH
Rajesh

TAX ASSESSMENT BASIS MISSING IN SEGMENT E1EDK04 FOR IDOC INVOIC

Hello,
Tax assesment basis is missing in segment E1EDK04 for IDOC INVOIC. In EDI messages,Tax assesment basis has to be sent in TAX segment together with VAT rate. When there is only one VAT rate this is not a problem as tax assessment basis is the total net amount (And we have it in the IDOC). On the other hand when there is more than one VAT rate in the invoice, we don't have in the IDOC the Tax assesment basis of each VAT rate.
Did someone experience this issue ? How did you handle it ?
Regards.
Eric.

Dear Eric
The latest pack available now for these components are (for PI 7.1)
SAP BASIS 7.11 support package 6
SAP HR 6.04 with Support Package 44
If you are in PI 7.0 then I suggest you download the latest patch from marketplace.
Sourabh

How can i pass the segments and fields to the ORDERS05 IDOC

Hi All,
I want to use ORDERS05 Idoc type for creating sales order. How can I pass the order type, sales org., distr. channel, division, sold-to-party, material and quantity to the Idoc?
please help me out in this.
thanks in advance
jasmine

Hi,
Goto WE19 TC and there select your IDOC and there u can pass the data.
Regards,
Phani

IDOC format for ORDERS05

Hi all,
I have search through the web and in sap.com and I haven´t found the specification (details of fields and their meanings) for the standart idoc ORDERS05.
Does anyone on the forum knows where i can find this information?
(I have no access to a SAP system).
Thanks for all.

Structure of basic type ORDERS05
Purchasing/Sales
E1EDK01 : IDoc: Document header general data
Status: Required , min. number : 1 , max. number : 1
Structure
E1EDK14 : IDoc: Document Header Organizational Data
Status: Optional , min. number : 1 , max. number : 12
Structure
E1EDK03 : IDoc: Document header date segment
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDK04 : IDoc: Document header taxes
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDK05 : IDoc: Document header conditions
Status: Optional , min. number : 1 , max. number : 16
Structure
E1EDKA1 : IDoc: Document Header Partner Information
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDKA3 : IDoc: Document Header Partner Information Additional Data
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDK02 : IDoc: Document header reference data
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDK17 : IDoc: Document Header Terms of Delivery
Status: Optional , min. number : 1 , max. number : 4
Structure
E1EDK18 : IDoc: Document Header Terms of Payment
Status: Optional , min. number : 1 , max. number : 3
Structure
E1EDK35 : IDoc: Document Header Additional Data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1EDK36 : IDOC: Doc.header payment cards
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDKT1 : IDoc: Document Header Text Identification
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDKT2 : IDoc: Document Header Texts
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1EDP01 : IDoc: Document Item General Data
Status: Optional , min. number : 1 , max. number : 999999
Structure
E1EDP02 : IDoc: Document Item Reference Data
Status: Optional , min. number : 1 , max. number : 10
Structure
E1CUREF : CU: Reference order item / instance in configuration
Status: Optional , min. number : 1 , max. number : 1
Structure
E1ADDI1 : IDoc: Additionals
Status: Optional , min. number : 1 , max. number : 999999
Structure
E1EDP03 : IDoc: Document Item Date Segment
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDP04 : IDoc: Document Item Taxes
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDP05 : IDoc: Document Item Conditions
Status: Optional , min. number : 1 , max. number : 16
Structure
E1EDPS5 : A&D: Price Scale (Quantity)
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDP20 : IDoc schedule lines
Status: Optional , min. number : 1 , max. number : 9999
Structure
E1EDPA1 : IDoc: Doc.item partner information
Status: Optional , min. number : 1 , max. number : 8
Structure
E1EDPA3 : IDoc: Document Item Partner Information Additional Data
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDP19 : IDoc: Document Item Object Identification
Status: Optional , min. number : 1 , max. number : 5
Structure
E1EDPAD : A&D: Material Exchange
Status: Optional , min. number : 1 , max. number : 1
Structure
E1TXTH1 : General Text Header
Status: Optional , min. number : 1 , max. number : 1
Structure
E1TXTP1 : General Text Segment
Status: Optional , min. number : 1 , max. number : 100
Structure
E1EDP17 : IDoc: Document item terms of delivery
Status: Optional , min. number : 1 , max. number : 5
Structure
E1EDP18 : IDoc: Document Item Terms of Payment
Status: Optional , min. number : 1 , max. number : 3
Structure
E1EDP35 : IDoc: Document Item Additional Data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1EDPT1 : IDoc: Document Item Text Identification
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1EDPT2 : IDoc: Document Item Texts
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1EDC01 : SS: Service specifications general data
Status: Optional , min. number : 1 , max. number : 9999999
Structure
E1EDC02 : SS item: Reference data
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDC03 : SS item: Date segment
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDC04 : SS item: Taxes
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDC05 : SS item: Conditions
Status: Optional , min. number : 1 , max. number : 16
Structure
E1EDC06 : Service line formula fields
Status: Optional , min. number : 1 , max. number : 1
Structure
E1EDC07 : Service line user fields
Status: Optional , min. number : 1 , max. number : 1
Structure
E1EDCA1 : SS items: Partner information
Status: Optional , min. number : 1 , max. number : 8
Structure
E1EDC19 : SS items: Object identification
Status: Optional , min. number : 1 , max. number : 5
Structure
E1EDC17 : SS items: Terms of delivery
Status: Optional , min. number : 1 , max. number : 5
Structure
E1EDC18 : SS items: Terms of payment
Status: Optional , min. number : 1 , max. number : 3
Structure
E1EDCT1 : SS items: Text identification
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1EDCT2 : SS items: Texts
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1CUCFG : CU: Configuration data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1CUINS : CU: Instance data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1CUPRT : CU: part-of data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1CUVAL : CU: Characteristic valuation
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1CUBLB : CU: Configuration BLOB (SCE)
Status: Optional , min. number : 1 , max. number : 999999
Structure
E1EDL37 : Handling unit header
Status: Optional , min. number : 1 , max. number : 999999
Structure
E1EDL39 : Control Segment for Handling Units
Status: Optional , min. number : 1 , max. number : 9
Structure
E1EDL38 : Handling Unit Header Descriptions
Status: Optional , min. number : 1 , max. number : 1
Structure
E1EDL44 : IDoc: Handling Unit Item (Delivery)
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1EDS01 : IDoc: Summary segment general
Status: Optional , min. number : 1 , max. number : 5

Problem in Idoc extension for ORDERS05

HI all,
Am facing problem in inbound idoc, we have extended the Idoc ORDERS05 with one custom segment, and written the code in user exit EXIT_SAPLVEDA_001 and include ZXVEDU03 exit is triggering properly, sales orderis genarted successfull, but z-fileds are not updating in VBAK table,
so plz help....
Regards,
Suresh.D
Edited by: suresh dameruppula on Oct 20, 2009 2:39 PM

Hi Suresh,
The function exit and the include what you found is to read data from the IDOC segment into either internal table or structure.
That's the first step which you have done is part of the below set:-
EXIT_SAPLVEDA_001 & ZXVEDU03
Now you need to populate the which you have read from the idoc into the document for that you need to write the code in the below set. The below one is a function exit which will be called during the BDC. You can see this below
Aufruf Transaktion Auftragerfassung VA01                             *
call transaction Order Entry VA01                                    *
        CASE xaprau.
at line number 131 in the function module IDOC_INPUT_ORDERS.
EXIT_SAPLVEDA_002 & ZXVEDU04
Please let me know if you still have any further queries.
Thanks,
Mahesh.

IDOC-Orders05 extension for Inbound process

Hi experts,
Here am struggling with one IDOC requirement,the requirement is Updating the data for the three fields in VBKD through inbound idoc.
since those fields are standard fields that is missing in the segment of standard IDOC-Orders05,so here am doing the extension of orders05 the basic steps like segment creation,assigning message type,assigning functional module has been done,now am copied the standard function module IDOC_INPUT_ORDERS to Z and now i have to find out the exact point where i have to insert my logic to update those fields.
No where am finding the option to modify the VBKD table,Can you please help me on this.

Hi Dinesh,
Please try to use BAPI 'BAPI_CUSTOMERCONTRACT_CHANGE' to update your required data in VBKD table , Please use this BAPI in inside your IDOC FM.
Below Sample code are there , Please try to use.
d_VBELN = '50000172'.
contract_header_inx-updateflag = 'U'.
CLEAR contract_items_in.
contract_items_in-itm_number = '100'.
contract_items_in-material = 'H51-YY019'.
contract_items_in-target_qty = '2'.
APPEND contract_items_in.
contract_items_inx-updateflag = 'U'.
contract_items_inx-itm_number = '100'.
contract_items_inx-material = 'X'.
contract_items_inx-target_qty = 'X'.
APPEND contract_items_inx.
CALL FUNCTION 'BAPI_CUSTOMERCONTRACT_CHANGE'
EXPORTING
SALESDOCUMENT = D_VBELN
contract_header_in = contract_header_in
contract_header_inx = contract_header_inx
TABLES
return = return
contract_item_in = contract_items_in
contract_item_inx = contract_items_inx.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
Regards,
Prasenjit

The IDOC-SDATA for the segment E1EDP01 does not have the whole value passed

HI
I am triggring the ORDERS05 Idoc from TCode - WE19 .
In the E1EDP01 segment I have populated the quantity field , UOM field , currency field and the plant field.
I am facing the issue
1) It is not updating the plant field in R/3 orders that are created .
2) I debugged the code and found that the data for the currency field and the plant field is not being pulled in the IDOC-SDATA for the segment E1EDP01 .
Any idea why is this happening
Thanks
Nikhil

HI
I got the answer for it.
This has to be delt in the E1EDP02 segment with the qualifier value as 083 and the document value as the plant
Thanks
Nikhil

Idoc qualifier for field ihrez segment e1edp02

Hi all,
I am using field ihrez of segment e1edp02 twice for posting the reference ( ship to ref and sold to ref)...I could find the idoc qualifier for ship to reference is 44 ..what can i use for sold to reference.. can somebody help me with this please.
Thanks,
Kiran..

Hi ,
I am also Facing the same problem i am able to pass the reference value for ship to party using Qualifier 044..but not able to pass the value for sold to party..
please help me if u got the solution in your case..
Regards
-Arun

IDOC Type for Tcode CC01 and CC02 (Create / Change Change Numbers)

We are trying to integrate Change Master from a 3rd party system to SAP R/3 4.72.What is the IDOC Type for Tcode CC01 and CC02 (Create / Change Change Numbers)

Thanks...
We have looked at this IDOC Type. However we are not very sure how the components (Material/BOM etc.) will be mapped into E1AEEFM segment in the IDOC.

Mandatory segments and fields of Idoc...

Hi Experts,
I am very keen to know the mandatory segments and fields of the ORDERS05 IDOC so can you please let me how to check the mandatory feilds and segnents of this particular Idoc.
Thanks in advance.Your help is highly appreciated.
Thanks,
Kiran.

Hi,
U can check in WE60 transaction code where u have to specify the basictype ORDERS05 AND THEN CLICK ON HTML FORMAT BUTTON..Now u can see the documentation of the idoc...
Regards,
Nagaraj

Segments E1EDK04 and E1EDK05 in IDOC ORDERS05 for PO's

Similar Messages

Maybe you are looking for