Segment E1EDL44 in orders05

HI,
I want to populate E1EDL44 segment in orders05.what is the user exit.
thanks in advance.

http://www.jt77.com/CRM/related-discussion-5928.html

Similar Messages

Segment management in ORDERS05 IDOC.

Hi there.
I have two questions, one is very focused on text management in ORDERS05, the other one is more generally speaking.
1 - Text management in ORDERS05 IDoc:
I have texts in my purchase order that I fill in, and then generate my IDoc. When looking at IDoc detail through WE05 or WE02, my texts are not visible neither in E1EDKT1 nor E1EDPT1 segments. Basically, those segments are not even created in my IDoc. Why? Anything to do in PO and/or ALE customizing?
2 - More general:
I need to have, in my E1EDS01 segment, the total quantity I order in my PO. So, I need a segment with qualifier '004' in SUMID, then my quantities. Currently, I only have SUMID='002' and my total value amount. How can I define (or it is defined by the system) the type of information I have in my segments, or segments themselves?
Please tell me if not clear at all.
Thanks for your answers.
Chris.

Thanks Dani.
I checked the T166A table and found that the following entries are missing for my cases: EKPO and EKKO for my ZNB PO type.
Shall I just put an entry for those two things in that table and this will allow me to get my texts in my ORDERS05 IDoc?
For point 2, as I am not an ABAP developper, I do not understand what to do. I can deal with customizing, but not with ABAP programming on that subject.
Thanks anyway at least for the first part of the answer.

Specific segment in idoc ORDERS05

Hi,
In purchase order, we have idocs in type ORDERS05. Someone has added specific segment under standard segment E1EDPA1.
In scheduling agreement release we have also idocs in type ORDERS05 but not the specific segment added.
Do you know in which user exit or else, there can be condition in the system which add specific segment in OREDERS05 when it is purchase order, and do not add specific segment when it is scheduling agreement release... Because I want to modifiy it to add also specific segment in scheduling agreement releases..
Thank you for your help.
Regards,
Peggy Delvincourt

Hello Madhu
The specific segment already exist (old team has create it to put others data) in the idoc type ORDERS05.
But and I do not understand why this specific segement appears only for purchase order but not in scheduling agreement release, as theses 2 types of documents are the same idoc type ORDERS05.
I think a specific code is wriiten to put "if purchase order create specific segment in ORDERS05, if not purchase order do not create specific segment in ORDERS05".
And I can't find where this condition might be, in any user exit?
Because I need to correct that and make the system create the specific segment also for scheduling agreement release...
Hope I'm clear..
Thank for your help.
Peggy.

Item Segments in the ORDERS05

Hi,
I have the ORDERS05 extended .
I have extended the segment E1EDKT2 with the custom segment.
I will be having the multiple lines to be appeded into the custom segment
How can i do that ?
READ TABLE dint_edidd WITH KEY segnam = 'E1EDKT2'.
lv_tabix = sy-tabix.
CLEAR dint_edidd.
ADD 1 TO lv_tabix.
MOVE 'XXXX' TO l_z1sdeue-con_type.
MOVE 'XXXX' TO l_z1sdeue-pieces.
MOVE: 'Z1SDEUE' TO dint_edidd-segnam,
l_z1sdeue TO dint_edidd-sdata.
INSERT dint_edidd INDEX lv_tabix.
This is working fine for one line.
How can i handle for multiple lines ?
Thanks.
Rohita.

Solved

Need segment & field from ORDERS05

Hi,
I was trying to find the corresponding segment and field for VBKD-INCO1 [Incoterms (part 1)] from ORDERS05 idoc.
Please help me in this regard.

Hi Ramesh,
Please check segment E1EDK17-LKOND with QUALF = '001'.
Regards,
Ferry Lianto

How to get optional segments of Basic type ORDERS05

Hi All,
I am using ORDERS05 Basic type for one implementation where I need to use segment E1CUCFG of this basic type but it is not coming as this is optional segment. Please let me know how to get it.
Thanks !!

Hi,
In WE30, I can see the segment E1CUCFG for ORDERS05, If you want to use that, you will have to populate the same.
Regards,
Amitava

IDoc ORDERS05 - Configuring IDoc Segments

Hi All,
Needed some help on understanding how to configure a new idoc using an extended SAP standard idoc type.
I'm using the ORDERS05 idoc type and extending it to add a single segment (example extended idoc type: ZORDEXT). We're creating a new condition type to trigger the idoc after sales order create/change. I'm planning to use the standard FM IDOC_OUTPUT_ORDRSP to create the idoc.
I noticed that only 1 segment in the ORDERS05 is set to mandatory (E1EDK01). We have identified at least 10 other required segments in the standard idoc which we need to populate with data. How do I configure the idoc to populate those segments? Do I need to set them as mandatory in a customer exit?
Thanks in advance.
Cal

I would have thought that the easiest place to strip out all the unwanted segments would be in your Middleware. Otherwise, you should be able to strip the segments out by creating an include in one of the Customer Functions in IDOC_OUTPUT_ORDRSP, i.e.
CALL CUSTOMER-FUNCTION '004'
CALL CUSTOMER-FUNCTION '001'
CALL CUSTOMER-FUNCTION '003'
Cheers, Paul.

Problems with idoc ORDERS05

Hi experts,
I created a new Z segment for idoc ORDERS05 and it works fine. This idoc is generated whenever a PO is created or modified. But if the PO has locked or deleted items, there is no segment for this items in the IDOC. Should I modify any code or something in SPRO??
Thanks in advance,
Maria

Hi again...
I'm trying to make a copy of the standr FM IDOC_OUTPUT_ORDERS because I think it may be easier to add the segments I need. I have also created in tx. WE41a new operation code ZME10 with my new fm. An in tx. WE20 I have assigned ZME10.
The problem is when I run ME9F i get this error:
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC',
was neither
caught nor passed along using a RAISING clause, in the procedure
"NEW_DYN_PERFORM" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
The program "RSNASTED" contains the CALL FUNCTION statement.
The name of the function module to be called is "ZIDOC_OUTPUT_ORDERS".
but "ZIDOC_OUTPUT_ORDERS" cannot be found in its function group.
Any idea ??
thanks in advance !

Help on ORDERS05 IDoc mapping..

Hi Experts,
   Please help me out in finding out the IDoc Segment fields(ORDERS05) equivalent to the following SAP fields.
20 Quantity             VBAP KWMENG Num(6)
21 Unit of Measure VBAP VRKME      Char(3)
22 Gross Price       KONV KBETR       Curr(11.2)
23 Discount           KONV KBETR       Curr(11.2)
24 Surcharge         KONV KBETR       Curr(11.2)
25 Net Value         KONV KBETR       Curr(11.2)
26 Cost Object
31 Payment Terms VBKD ZTERM      Char                E1EDK01 -ZTERM
32 Footer Msg1      STXI     n/a             Char
33 Footer Msg2      STXI     n/a             Char
34 Footer Msg3      STXI     n/a             Char
35 Total                 KONV KBETR       Curr                E1EDS01 -SUMID (004)
       I thought for
           Quantity               : E1EDP01-MENGE
           Unit of Measure    : E1EDP01-MENEE
           Gross Price          : E1EDP01-PREIS
           But when i went to WE19 and posted the idoc by populating the above segment fields its not getting updated in the sales order, instead in the created sales order it shows quantity as 0 and its not getting updated.
     so iam not sure whether these segment fields (in ORDERS05 IDoc) are the right fit for quantity, UoM and Gross price. Please provide me the correct segment fields mapping for the above SAP fields.
     Actually Gross price, surcharge, discount and Net value are calculated automatically by SAP while creating the sales order based on the amount and quantity entered - right..? Then do i need to populate the values for these fields also in IDoc for testing using WE19.
     Please reply me.
    Thanks in advance,
    karthik.

In sales order,these quantity updating in Tatget quantity,look at VBAP Table ..
You will get good idea..
Reward Points if it is helpful
Thanks
Seshu

Import segment structure from R3 to XI

Hi,
I realize an Abap mapping for an idoc to file scenario . Thus in my coding, I need to define some internal structures which are exactly the same than segment E1EDP01 (idoc orders05 ).
In XI , tcode SE11 i can see some idoc structures (like E1EDP10, E1EDP13) , but this one doesn't exis.
Is is possible to import this structure from R/3 to XI ? Or must I define manually in my code the same structure than in R/3 ?
Regards.
Carme

> I realize an Abap mapping for an idoc to file scenario .
I am not sure why you need an ABAP Mapping for and IDOC to File secnario. Can you explain it further?
>
> In XI , tcode SE11 i can see some idoc structures (like E1EDP10, E1EDP13) , but this one doesn't exis.
Again I am not sure why to do this in SE11.
> Is is possible to import this structure from R/3 to XI ? Or must I define manually in my code the same structure than in R/3 ?
In XI we use IDX2 transaction to update the IDOC metadata. OR we import it in XI Repository under imported objects in one the SWCV.
Regards,
Sarvesh

ORDERS05 Idoc Type Extension

Hello,
I am extending the segment E2EDKA3 in ORDERS05. Please let me know any user exit or any other way to populate the values in the extended segments.
I am adding these fields: VBPA-KUNNR,VBPA-ADRNR,VBPA-XCPDK & VBPA-ADRNP                         .
Thanks in advance,
Suresh

Hi Suresh,
Go through this info ucan able to do.
Enhancement of IDoc Type
Usually enhancement takes place when the content in IDocs provided by SAP are not sufficient for the business process. IDoc extension can take place whenever dictionary table has a new structure appended required by the business process.
In brief IDoc extension takes place when extra fields are required for the business process.
Let us take a scenario and understand the process of IDoc extension.
In this scenario say visitor is different from the actual customer who has came to the sales office in behalf of the customer to obtain the quotation or inquiry etc. Or an authorized agent qualified by the actual customer to order for items. So a field by name NAMEVI (Visitor) is added to Customer master data. As there is no provision given by SAP to handle this, we need to extend an IDoc.
The standard message type and IDoc type provided by SAP are DEBMAS and DEBMAS05.
Consider the data in the table below for extending the IDoc. These details can be understood in different sections in the process of extending it.
Basic IDoc type      DEBMAS05
Version      4.7
IDoc extension      DEBMASEXT
Custom segment      Z1KNA1
Fields in Custom Segment      Visitor
Parent of Custom Segment      E1KNA11
Outbound process
Step1. Customize kna1 table by appending a structure provided by SAP (ZAKNA1)
Component                Component Type
VISITOR                     NAMEVI
Step2: Write a module pool program to update some existing customers to add data for Visitor.
Step3: Create a custom segment
Transaction Code: WE31
Segment type: Z1KNA11   Click (create). Provide short text
Field Name                Data element
VISITOR                NAMEVI
Save
Step4: Create IDoc extension
Transaction      WE30
Object Name      DEBMASEXT
Choose Extension
Click   and it leads to next screen.
Linked basic type: DEBMAS05
Provide description and enter
Observe all the segments to be copied into your IDoc extension from linked basic
type.
Select E1KNA11 and click (create segment) to obtain a popup window
Provide the required values and observe child segment Z1KNA11 to be added to
parent segment E1KNA11.
Step5: Release segment and IDoc extension
Transaction: WE31
Segment type: Z1KNA11
Path: Edit à Set release
Step6: Assign Basic type to extension / messages
Transaction: WE82
Click , then
Select DEBMAS message type against DEBMAS06 basic type
Click   provide the information
Message Type      Basic Type      Extension      Version
DEBMAS      DEBMAS06      DEBMASEXT           4.7
Delete the earlier one from which it was copied.
Save.
Observe the result as follows
Step 7: Check and Transport IDoc extension
Transaction: WE30
Object name: DEBMASEXT
Path: Development object à Check
Ensure that there are no errors or warnings
Now transport
Path: Development à Transport
Step8: Find suitable user exit for writing code to support IDoc extension
Transaction: SE84.
Click Enhancements
In short text provide customer
Find suitable enhancement to be VSV00001
                         Alternative way
Transaction: SMOD
Click F4 help for Enhancement
Path: F4help à SAP Applications à Logistics general à Logistics Basic Data à
Business partners à Vendor Master.
Find the enhancement as VSV00002, which is an approximate user exit.
Now search for different extensions like VSV00001. Then see for its components.
Identify the appropriate user exit to be EXIT_SAPLVV01_001 (Create Export of
Additional Customer Master Segments). This user exit can be used in outbound ALE
process, meant for filling the data into custom segments.
You have to identify here another user exit as EXIT_SAPLVV02_001, which is
helpful for inbound ALE process. This user exit can be used to read the segments
and post it to Application repository.
Step9: Develop a project to encapsulate enhancements and components.
Transaction: CMOD.
Enhancement: custex and click Create to provide attributes.
Click Enhancement Assignments.
Provide VSV00001, short text and save.
From the initial screen of the transaction, select components and click change.
Find 4 components to be added.
Activate them.
Select user exit EXIT_SAPLVV01_001 for outbound process and double click it. It leads to function builder.
Double click on provided include program ZXVSVU01 and press enter.
Now, write supporting code for IDoc extension, i.e., populating custom segments in IDoc.
Check the code and activate.
Code in ZXVSVU01
*& Include           ZXVSVU01                                         *
*In this scenario, the E1KNA11 has been extended to accommodate
*User-defined fields in the customer table kna1. The name of the
*extended
*segment is z1kna11. There is one custom field: visitor
*Data declarations
DATA: kna1m like e1kna1m,
      kna11 like e1kna11,
      z1kna11 like z1kna11,
      w_kna1 like kna1.
make sure you are processing correct message type
check message_type eq 'DEBMAS'.
make sure data is added after the correct segment
check segment_name eq 'E1KNA1M'.
since customer number is not passed in this user exit, you need to go
through the data records to find the customer number
loop at idoc_data.
case idoc_data-segnam.
     when 'E1KNA1M'.
       move idoc_data-sdata to kna1m.
     when 'E1KNA11'.
       move idoc_data-sdata to kna11.
endcase.                             " case idoc_data-segname.
endloop.                               " loop at idoc_data.
select data from the user-defined fields in kna11.
select single *
from kna1                            " Customer master table
into w_kna1
where kunnr = kna1m-kunnr.
if sy-subrc eq 0.
set the idoc extension name for control record
idoc_cimtype = 'DEBMASEX'.
clear custom fields from kna1 to extended segment
clear z1kna11.
copy custom fields from kna1 to extended segment
move-corresponding w_kna1 to z1kna11. " field name must be same
condense all fields of extended segment
condense: z1kna11-visitor.
populate segment name in the data record, copy data contents into it
and append the data record to existing data records in
move 'Z1KNA11' TO IDOC_data-segnam.    " administrative section
move z1kna11 to idoc_data-sdata.       " data section
append idoc_data.
endif.                                 " if sy-subrc eq 0.
Step 10:
Define Logical System
Assign client to Logical System
Maintain RFC Destination
Maintain Customer Distribution Model
Generate Partner Profiles
Distribute Customer Distribution Model
INBOUND PROCESS
Step 11: Append the custom structure to the table KNA1 similar to the process done
        in outbound process.
Step 12.
Define Logical System
Assign client to Logical System
Generate Partner Profiles
Step 13. Execute the transaction to Send Customers from Outbound system.
Step 14. Now in the Inbound system, create the project in the similar way as done at
        outbound side.
In the user exit EXIT_SAPLVV02_001, find include ZXVSVU02. Write the code to
support IDoc extension.
Code in ZXVSVU02
*& Include           ZXVSVU02                                         *
data: kna1m like e1kna1m,
      kna11 like e1kna11,
      z1kna11 like z1kna11.
data fs_kna1 type kna1.
message i000(0) with 'INBOUND PROCESS CALLED'.
LOOP AT IDOC_data.
case idoc_data-segnam.
    when 'E1KNA1M'.
      kna1m = idoc_data-sdata.
    when 'E1KNA11'.
      kna11 = idoc_data-sdata.
    when 'Z1KNA11'.
      z1kna11 = idoc_data-sdata.
      select single *
        from kna1
        into fs_kna1
       where kunnr = kna1m-kunnr.
      if sy-subrc eq 0.
        update kna1
           set visitor = z1kna11-visitor
         where kunnr = kna1m-kunnr.
      else.
        idoc_status-docnum = idoc_control-docnum.
        idoc_status-status = '51'.
        idoc_status-msgty = 'E'.
        idoc_status-msgid = 'ZE'.
        idoc_status-msgno = '005'.
        idoc_status-msgv1 = kna1m-kunnr.
     append idoc_status.
      endif.                           " if sy-subrc eq 0.
endcase.                             " case idoc_data-segnam.
endloop.                               " LOOP AT IDOC_data.
Step 15. Assign FM to extension/Message type
Transaction:      WE57
Path: Change à New Entries
Select IDOC_INPUT_DEBITOR against DEBMAS06 basic type, to fill extra
information as shown below.
Function Module          Basic Type     Message Type          Extension
IDOC_INPUT_DEBITOR     DEBMAS06     DEBMAS          DEBMASEXT
Step 16. Execute the transaction to Get Customers.
And observe that records with extra data are saved in database.
Rewards some points.
Rgds,
P.Nag

Segment Namespace Error

Hi,
Am using the SEGMENT_DELETE function which in turn uses SEGMENT_NAMING_CHECK.
My requirement is to suppress an standard segment E1EDL44 if the E1EDL44-VELIN EQ 3.
Unfortunately, it is giving me an error in segment_delete stating as "Name E1EDL44 not permitted in CUSTOMER system"
At the same time, if i give a ZE1EDL44 segment , it does not give me any error.
Is there no way that one can suppress the standard segment via an user exit.
I am using delivery idoc to suppress this segment.
Regards
Krish

Came to an conclusion that we are never supposed to delete an standard segment and is not good practice. So decided to handle it in XI with Premap.

Idoc syntax errors

Hi all,
Im developing a interface for purchase/sales orders. i populated the fields into segments and am running the function module. it is creating an idoc with status 60
EDI: Syntax error in IDoc (segment cannot be identified).
I dont know which segment its not identifying..
mesage type ZXXXXXX
process code used orde
fm idoc_input_orders.
can somebody help me with this in trouble shooting
thanks,
Kiran

Hi Vijay,
this is the structure of edidc when i c it in we19..dont know how to clear this error.
EDIDC   2000000000000404101620 60        2SAPSD1    LSSD1CLNT200
E1EDK01
       E1EDK14                     0081800
       E1EDK14                     00710
       E1EDK14                     00610
       E1EDK14                     012ZOR
       E1EDK14                     019OMY
       E1EDK03                     00220040809
       E1EDK03                     02200000000
       E1EDK03                     02300000000
       E1EDKA1                     AG 0002200253
       E1EDKA1                     VE 00000096
       E1EDK02                     001CUSTPONOTEST1
       E1EDK02                     044J0000000143
    4 E1EDKT1                     Z004I    VBBK
    4 E1EDKT1                     Z002I    VBBK
    4 E1EDP01                     000001     0000000010     PCE
       E1EDL44                     1
this is the erro message im getting..
The segment E1EDL44 does not occur at the current level of the basic type ORDERS05 (extension ).
This error can have several reasons:
The segment E1EDL44 is assigned to a group whose header segment does not occur.
The segment E1EDL44 does not exist in the syntax description of the basic type ORDERS05 (extension ).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type ORDERS05 (extension ).
thanks..

User exit for Sales order

hi,
i need to eliminate leading zeros for PO number which comes in SO created trough ALE.i found the enhancement for the FM idoc_input_orders.in that enahancement we have 12 FM's.my Leading zeros are comming for field belnr which comes in e1edk01 segment of idoc orders05.now i had coded my part of coding in FM exit_saplved.._oo1 and i had activated that.but it is not working for me.than i tought of going to other FM exit_sapl..._009.in which i'm not able go into the include either.plz help me out.thank you.

Hi, Krishna!
With IDOC_INPUT_ORDERS during IDoc interpretation PO number is assigned to XVBAK-BSTKD field which is later used for sales order creation with reference to PO.
So all you need is to use some customer exit with changing parameters containing XVBAK after IDoc interpretation is completed. For example you can use EXIT_SAPLVEDA_009 which is called at the end of IDoc check after interpretation.
Regards,
Maxim.

Packing at Shipment Level

Hi All,
I am trying to do packing at shipment level using IDocs. I am using IDoc type SHPMNT04 with message as SHPMNT. The process code which we are using is SHPM with Function module IDOC_INPUT_SHPMNT. Idoc type SHPMNT04 has segment E1EDL44 where we can give the Handling units details which needs to be used for packing. But no where in the process code, the system is processing this segment and hence packing is not working with this Idoc type.
Can you please help me to do packing using Idoc type SHPMNT04.
Regards,
Shaju

Select all the handling units and goto-Extra and select - Generation of SSCC number and system will generate teh SSCC number ranges as u have set.
Regards
Sunil

Segment E1EDL44 in orders05

Similar Messages

Maybe you are looking for