Problem about Idoc Segment Conversion
Hi experts,
When i configured the Idoc conversion in the Sender system, it was correct. But it doesn't work after configuring the Idoc conversion in the Receiver system. The case like this: the Idoc record generated in the Sender system but doesn't generated in the Receiver system.
I will be appreciate if anyone can help me!
can not be solved
Similar Messages
-
Hi, everybody.
This time, I'm developing a IDOC Receiver though the SAPIDocReceiver class. With the dotnet Connector manual from SAP, the receiver side on dotnet is easy to develop. But how to configure the SAP R/3 to send IDOC to the dotnet side, I can't find the clear steps in the manual.
So I searched some material about how to configure IDOC, and hope it will be useful to my work. But most of them mainly focus on how to configure a IDOC transformation between SAP system but not NON-SAP system.
So what I want to ask is IS there some difference with the two configuration, I mean the SAP to SAP one and the SAP to NON-SAP one. I guess the difference should be have. Are the necessary configure step like create a logic system, allocate logical systems to clients and so on also necessary under the NON-SAP case? I think some of the configure actions is different in this two case. Can anyone give me some clear steps or tell me where I can get them?
thanks to all.Hi,
for testing purposes you can do the following:
(1) via SM59 create the RFC destination for your dotnet application
(2) via WE21 create a trfc-port pointing to the RFC destination created in (1)
(3) via SM30 maintain view V_TBDLS to create a new logical system for your dotnet application for example DOTNET (and maybe for the SAP client you are testing with - here the name could be for example <SID>CLNT<CLIENT>)
(4) via SCC4 assign the logical system to the SAP client (for example <SID>CLNT<CLIENT>) only if not already maintained.
(5) In WE20 create a partner profile for logical system created for the dotnet application in step (3)
(6) In WE20 add outbound parameters for the message type (for example MATMAS) and idoc type (MATMAS03) you want to send. As partner port use the trfc-port of step (2)
(7) In WE19 create an IDoc via basic type (the idoc type used in step (6), for example MATMAS03) and maintain the following fields in the control record EDIDC:
<b>recipient port</b> the port created in step (2)
<b>recipient partner number</b> the logical system name of the dotnet application created in (2)
<b>recipient partner type</b>'LS'
<b>sender port</b> SAP<SID>, where SID is the SAP system id
<b>sender partner number</b> the logical system name the SAP client maintained in step step (4)
<b>sender partner type</b>'LS'
<b>message type</b> the message type used in step (6), for example MATMAS
In the other segments E1* you can fill in whatever you like
Hit the push button "Standard outbound processing"
(8) you can check if the IDoc has been sucessfully created by BD87. If an error has occurred in the receiving application or there is any other error you can also see it here. Maybe the IDoc is not passed to the receiver, then you can process the IDoc also from here.
This is how you can create your test environment. If you want to get the IDoc created form the SAP application it depends on the application how to do that!
Best regards,
Willy -
Problem with Idoc segment maximum length
Hi friends,
We are now creating a new Idoc type. We have started to create the first segment but we encountered a major problem.
The problem is that we have a field of 4000 characters but the limit of all segment fields together is 1000 characters.
Is there any way to change this limitation or another way to define Idoc?
Thanks in advanced,
Udi Dekel.Hi,
When you create a segment that exceeds the max length, SAP automatically creates a child segment for the exceeded length. For your problem though, you can create 4 segments of length 1000 each and split the data in these 4 segments and then concatenate the data later in the idoc processing function module. On the other hand if it is an outbound idoc, you can ask the receiving system to do the same.
Best regards,
Advait -
Problem in IDOC segment E1MTXLM
Hi all,
Basic type : MATMAS05
One of the segments is E1MTXLM has the data as below
"Heater assy., with NTC <(>&<)> protector, 240V, 3000W"
where as in the MM03 transaction Basic data text is shown as below
"Heater assy., with NTC & protector, 240V, 3000W"
I think there is problem while the IDOC is getting created but i have no idea what could be the problem.
Can any help in this regard.Hi Nejuma,
I don't think there is any problem with cofiguration settings.u r getting the idocs for some vendors .
if iam not wrong u r giving LS in the tcode(we20).The method which u r using is change pointers.As u r using standard idoc all the settings will be done.
Only settings u have to do is
1>generate partner profiles(WE20)
2>Distribute model view(BD64).
REGARDS,
Nagaraj -
Looping problem in idoc segments
Dear all,
I have created a own message type for material master,with four segments.Here for one material there may be different order unit like BOX,PAL etc.
When i am sending a material to xml format Its creating all the four segment for each order unit when it gets changed. I want only the order unit segment should repeat for one material.
Is there any looping changes should made in the program or what else?
Plz help me ASAP.
Thanks & Regards,
Arun.
Edited by: Arun Kumaran on Aug 27, 2008 3:21 PMPlease check the segment number of occurance. It should set to 1 for each parent Material segment. Watch out for syntax error for segment structure.
I hope this will help to solve issue.
Regards,
Mahesh -
IDOC to flat File----Problem in File Content Conversion at receiver
hi experts,
I am doing a IDOC to flat file secnario.
My requirment is IDOCXI-Flat file
Format of flat file is like:--
Every segment in the IDOC will be converted into a single line of file(without any delimiter). So number of lines in flat file will be equal to number of segments in IDOC.
I am facing problem in File Content conversion.
Please help me out..
Thanks
JaideepCheck this doc...
[How To...Convert an IDoc-XML structure to a flat file and vice versa in XI 3.0 |https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a] -
Problem with creation of IDOC Segment Type
Hi,
I tried to create IDOC Segment Type Z1LFA1 but error
prompted "Structure Z1LFA1 already exist.".
I tried deleting it at se11 but prompted
"You cannot edit object R3TR TABL Z1LFA1 with the
standard editor"
and at sm30-TADIR, but prompted
with "Cannot delete object directory entry, object exists."
How will go about this??
Please help!
Thanks!hi,
yup, tried doing that on we31 but the segment does not exist yet.
we're currently upgrading from 4.6 to ecc, I think the structure
was tranferred to our ecc client but the idoc segment and idoc type were not. I'll just have to transport it then.
Thanks! -
Problem about extended IDOC(urgent)
Hi experts,
i have idoctype,extended idoc,and one include.. i need modify that according to the requirement.. here i will give the idoctype and extended idoc type and include program .. please help me where exactly i need to do the change and what are the steps required for the requirement..
Exact Requirement: Modify the program which populates the idoctype invoice02 and extension zinvoice02 , if netvalue is zero(vbrp-netwr = 0) then populate the idoc segment E1EDP01.E1EDP26 , BETRG WITH QUALF = # 011' WITH ZERO VALUE. curently segment is not populated.
Please help me in this and explain the steps required for this.
idoctype:invoice02
extended idoc:zinvoice02
include:ZXEDFU02
Here i am giving the include program
CASE dobject-kschl.
WHEN 'ZGRI' OR 'ZGDF' OR 'ZGRN' OR 'ZGAE'.
t_int_edidd[] = int_edidd[].
t_xtvbdpr[] = xtvbdpr[].
ta_xvbdkr = xvbdkr.
CASE int_edidd-segnam.
WHEN 'E1EDK01'.
ta_e1edk01 = int_edidd-sdata.
PERFORM get_shipment_data.
PERFORM get_route_data.
int_edidd[] = t_int_edidd[].
WHEN 'E1EDP01'.
Update segment E1EDP01
1. Update field E1EDP01-PSTYP
2. Accumulated net weight & quantity of batch split items against
E1EDP01 segment of the main invoice item.
ta_e1edp01 = int_edidd-sdata.
i_tabix = sy-tabix.
CLEAR: ta_e1edp02. "DIAG01+
PERFORM update_segment_e1edp01.
MOVE ta_e1edp01 TO t_int_edidd-sdata.
MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
Populate segment Z1EDP08
Fields: ZZDESPACTY_A, ZZACTYUOM
PERFORM validate_segment USING control_record_out-idoctp
control_record_out-cimtyp
'Z1EDP08'
CHANGING n_subrc.
CHECK n_subrc EQ 0.
PERFORM calc_invoice_item_zzdespacty_a. "DIAG02+
int_edidd[] = t_int_edidd[]. "DIAG02+
WHEN 'E1EDP02'. "DIAG01+
IF int_edidd-sdata(3) = '016'. "DIAG01+
ta_e1edp02 = int_edidd-sdata. "DIAG01+
ENDIF. "DIAG01+
WHEN 'E1EDP19'.
Populate segment Z1EDL24
Fields: Material Characteristics or Material Class '001'.
PERFORM validate_segment USING control_record_out-idoctp
control_record_out-cimtyp
'Z1EDL24'
CHANGING n_subrc.
IF n_subrc EQ 0.
ta_e1edp19 = int_edidd-sdata.
CASE ta_e1edp19-qualf.
WHEN '002'.
PERFORM get_mat_characteristic USING ta_e1edp19-idtnr.
PERFORM fill_segment_z1edl24.
int_edidd[] = t_int_edidd[].
WHEN OTHERS.
ENDCASE.
ENDIF.
WHEN 'E1EDP26'.
Populate segment E1EDP26
Fields: BETRG
i_tabix = sy-tabix.
ta_e1edp26 = int_edidd-sdata.
IF ta_e1edp26-qualf = '001'. "Gross Price which is always present
PERFORM fill_segment_e1edp26.
int_edidd[] = t_int_edidd[].
ENDIF.
WHEN 'E1EDP08'.
Populate Segment Z1EDL37 *
Fields: Bespoke fields from Handling Unit (VEKP)
PERFORM validate_segment USING control_record_out-idoctp
control_record_out-cimtyp
'Z1EDL37'
CHANGING n_subrc.
CHECK n_subrc EQ 0.
ta_e1edp08 = int_edidd-sdata.
PERFORM fill_segment_z1edl37.
Populate Segment Z1EDP08 *
Fields: Total Despatch Activity *
PERFORM validate_segment USING control_record_out-idoctp
control_record_out-cimtyp
'Z1EDP08'
CHANGING n_subrc.
CHECK n_subrc EQ 0.
PERFORM calc_invoice_item_acty_total.
int_edidd[] = t_int_edidd[].
WHEN OTHERS.
ENDCASE.
WHEN 'ZGDW'.
Line above added line below removed - Assyst 73789
WHEN 'ZGIN'.
t_int_edidd[] = int_edidd[].
t_xtvbdpr[] = xtvbdpr[].
ta_xvbdkr = xvbdkr.
CASE int_edidd-segnam.
Start SU02
WHEN 'E1EDK01'.
ta_e1edk01 = int_edidd-sdata.
i_tabix = sy-tabix.
Get the conversion factor
PERFORM modify_exchange_rate.
MOVE ta_e1edk01 TO t_int_edidd-sdata.
MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
int_edidd[] = t_int_edidd[].
End SU02
*************************************************************SAM01 START
WHEN 'E1EDP02'.
Populate segment Z1EDP02
Fields: Reason code for sales order
ta_e1edp02 = int_edidd-sdata.
CASE ta_e1edp02-qualf.
WHEN '002'.
PERFORM fill_segment_z1edp02.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'Z1EDP02'
ta_z1edp02.
int_edidd[] = t_int_edidd[].
WHEN OTHERS.
ENDCASE.
***************************************************************SAM01 END
ENDCASE.
Start of JvdM01
WHEN 'ZGII'. "JvdM01
t_int_edidd[] = int_edidd[].
t_xtvbdpr[] = xtvbdpr[].
ta_xvbdkr = xvbdkr.
CASE int_edidd-segnam.
WHEN 'E1EDK01'.
Populate segment Z1EDKSH and Z1REM_STE_CDE
Fields: Shipment Number for Invoice
Reason code for sales order
ta_e1edk01 = int_edidd-sdata.
PERFORM fill_segment_z1edksh_ds.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'Z1EDKSH'
ta_z1edksh.
PERFORM fill_segment_z1rem_ste_cde.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'Z1REM_STE_CDE'
ta_z1rem_ste_cde.
int_edidd[] = t_int_edidd[].
WHEN 'E1EDKA1'.
Populate segment Z1EDKA1
Fields: Customer Account Group
ta_e1edka1 = int_edidd-sdata.
CASE ta_e1edka1-parvw.
WHEN 'RE'. "Bill To Party
PERFORM fill_segment_z1edka1.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'Z1EDKA1'
ta_Z1EDKA1.
int_edidd[] = t_int_edidd[].
ENDCASE.
WHEN 'E1EDP01'.
Read segment E1EDP01 for use later "JVDM02
ta_e1edp01 = int_edidd-sdata.
WHEN 'E1EDP02'.
Populate segment Z1EDP02
Fields: Reason code for sales order
ta_e1edp02 = int_edidd-sdata.
CASE ta_e1edp02-qualf.
WHEN '002'.
PERFORM fill_segment_z1edp02.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'Z1EDP02'
ta_z1edp02.
int_edidd[] = t_int_edidd[].
WHEN OTHERS.
ENDCASE.
WHEN 'E1EDP19'.
Populate segment Z1EDL24 and Z1EDP01 "JVDM02
Fields: Pack Size Activity for Material
Total Activity for Invoice Item
ta_e1edp19 = int_edidd-sdata.
CASE ta_e1edp19-qualf.
WHEN '002'.
PERFORM fill_segm_z1edl24_and_z1edp01.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'Z1EDL24'
ta_z1edl24.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'Z1EDP01'
ta_z1edp01.
int_edidd[] = t_int_edidd[].
WHEN OTHERS.
ENDCASE.
ENDCASE.
End JvdM01
ENDCASE.
Start SU02 Code Comment for implementing IR 340
**mpc01 - start of insert
start assyst 73789
*IF dobject-kschl = 'ZGDW'."amersham invoices
**IF dobject-kschl = 'ZGIN'."amersham invoices
end assyst 73789
CASE int_edidd-segnam.
for the organisation data header
WHEN 'E1EDK14'.
MOVE int_edidd-sdata TO ta_e2edk14.
where is qualifying organisation = 003 (delivering company code).
IF ta_e2edk14-qualf = '003' AND ta_e2edk14-orgid NE space.
SELECT SINGLE waers
INTO t001-waers
FROM t001
WHERE bukrs = ta_e2edk14-orgid.
IF sy-subrc = 0.
t_int_edidd[] = int_edidd[].
get the billing date for the invoice
LOOP AT t_int_edidd WHERE segnam = 'E1EDK02'.
MOVE t_int_edidd-sdata TO ta_e1edk02.
IF ta_e1edk02-qualf = '009'."billing date
w_fkdat = ta_e1edk02-datum.
EXIT.
ENDIF.
ENDLOOP.
if no invoice date use current date
IF w_fkdat IS INITIAL.
w_fkdat = sy-datum.
ENDIF.
change the general document header
LOOP AT t_int_edidd WHERE segnam = 'E1EDK01'.
i_tabix = sy-tabix.
MOVE t_int_edidd-sdata TO ta_e1edk01.
set the field to the default currency code for the company
ta_e1edk01-hwaer = t001-waers.
if the default value equals the idoc currency then exit
IF t001-waers = ta_e1edk01-curcy.
EXIT.
ENDIF.
get the exchange rates
SELECT *
INTO TABLE t_tcurr
FROM tcurr
WHERE kurst = 'NYB1' " SU01
WHERE KURST = 'GEBU' " SU01
AND fcurr = ta_e1edk01-curcy
AND tcurr = t001-waers.
IF sy-subrc NE 0."no values found
error the idoc
MESSAGE e400(vf) WITH c_exchange_rate_error
RAISING error_message_received.
EXIT.
ENDIF.
LOOP AT t_tcurr.
convert to date from inverted date to normal date format.
CALL FUNCTION 'CONVERSION_EXIT_INVDT_OUTPUT'
EXPORTING
input = t_tcurr-gdatu
IMPORTING
output = w_datum.
CONCATENATE w_datum+6(4)
w_datum+3(2)
w_datum(2)
INTO t_tcurr-datum.
MODIFY t_tcurr.
ENDLOOP.
sort the exchange rates with the newest first.
SORT t_tcurr BY datum DESCENDING.
read the first value in the table ie the newest.
LOOP AT t_tcurr WHERE datum <= w_fkdat.
EXIT.
ENDLOOP.
IF sy-subrc NE 0."no values found
error the idoc
MESSAGE e400(vf) WITH c_exchange_rate_error
RAISING error_message_received.
EXIT.
ENDIF.
Start SU01
Get the Exchange rate from the function module and populate
E1EDK01 TABLE
w_fcurr = ta_e1edk01-curcy.
call function 'CONVERT_TO_LOCAL_CURRENCY'
exporting
date = w_fkdat
foreign_amount = '0'
foreign_currency = w_fcurr
local_currency = t001-waers
type_of_rate = 'GEBU'
importing
exchange_rate = t_tcurr-ukurs
exceptions
no_rate_found = 1
overflow = 2
no_factors_found = 3
no_spread_found = 4
derived_2_times = 5
others = 6.
End SU01
ta_e1edk01-wkurs = t_tcurr-ukurs.
change the header data in segment
MOVE ta_e1edk01 TO t_int_edidd-sdata.
update the current idoc segment
MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
EXIT.
ENDLOOP.
update all of the idoc segments
int_edidd[] = t_int_edidd[].
ENDIF.
ENDIF.
ENDCASE.
*ENDIF.
**mpc01 - end of insert
End SU02 Code Comment for implementing IR 340Hi Venu,
Try with this code.
If vbrp-netwr = 0.
<b> WHEN 'E1EDP26.
CASE ta_e1edp26-qualf.
ta_e1edp26 = int_edidd-sdata.
WHEN '011'.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'e1edp26'
ta_e1edp26.
int_edidd[] = t_int_edidd[].
ENDCASE.</b>
ENDIF.
Thanks
Manju. -
Hi Gurus,
i have a problem in Idoc, while creating output type for a Billing document that time one segment repeating lots of time with same data..how to avoid this?
MohanaMohana
Are you sure about the segment name E1EDK01 ?? Becoz.. Only one Segment of type E1EDK01 is allowed in one IDOC...
See below for details:
Segm.type E1EDK01
Minimum number 1
Maximum number 1
Parent segment
Hier.level 1
Thanks
Amol Lohade -
Dear all,
Do you know the transaction or an document which give the link between the Qualifier segment of an segment IDOC and the SAP field ?
for example : IDOC ORDERS05
segment E1EDK03
qualifier 002 : wished delivery date in VA01
segment E1EDK02
qualifier 050 : Delivery Order in segment description but correspond to PO number in VA01
I search to fill in the field PO Date but I don't find the qualifer segment.
Could you please help me ?
thanks
VéroniqueHi friends,
i thing your problem will solve.
E1EDK01 : IDoc: Document header general data
Segment definition E2EDK01005 Released since Release 45B , Segment length: 0357
ACTION : Action code for the whole EDI message
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
KZABS : Flag: order acknowledgment required
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 002, Offset : 0066. external length : 000001
CURCY : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 003, Offset : 0067. external length : 000003
HWAER : EDI local currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 004, Offset : 0070. external length : 000003
WKURS : Exchange rate
internal data type : CHAR
Internal length : 000012 characters
Position in segment : 005, Offset : 0073. external length : 000012
ZTERM : Terms of payment key
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 006, Offset : 0085. external length : 000017
KUNDEUINR : VAT Registration Number
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 007, Offset : 0102. external length : 000020
EIGENUINR : VAT Registration Number
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 008, Offset : 0122. external length : 000020
BSART : Document type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 009, Offset : 0142. external length : 000004
BELNR : IDOC document number
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 010, Offset : 0146. external length : 000035
NTGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 011, Offset : 0181. external length : 000018
BRGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 012, Offset : 0199. external length : 000018
GEWEI : Weight unit
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 013, Offset : 0217. external length : 000003
FKART_RL : Invoice list type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 014, Offset : 0220. external length : 000004
ABLAD : Unloading Point
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 015, Offset : 0224. external length : 000025
BSTZD : Purchase order number supplement
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 016, Offset : 0249. external length : 000004
VSART : Shipping Conditions
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 017, Offset : 0253. external length : 000002
VSART_BEZ : Description of the Shipping Type
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 018, Offset : 0255. external length : 000020
RECIPNT_NO : Number of recipient (for control via the ALE model)
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 019, Offset : 0275. external length : 000010
KZAZU : Order Combination Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 020, Offset : 0285. external length : 000001
AUTLF : Complete delivery defined for each sales order?
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 021, Offset : 0286. external length : 000001
AUGRU : Order reason (reason for the business transaction)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 022, Offset : 0287. external length : 000003
AUGRU_BEZ : Description
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 023, Offset : 0290. external length : 000040
ABRVW : Usage Indicator
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 024, Offset : 0330. external length : 000003
ABRVW_BEZ : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 025, Offset : 0333. external length : 000020
FKTYP : Billing category
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 026, Offset : 0353. external length : 000001
LIFSK : Delivery block (document header)
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 027, Offset : 0354. external length : 000002
LIFSK_BEZ : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 028, Offset : 0356. external length : 000020
EMPST : Receiving point
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 029, Offset : 0376. external length : 000025
ABTNR : Department number
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 030, Offset : 0401. external length : 000004
DELCO : Agreed delivery time
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 031, Offset : 0405. external length : 000003
WKURS_M : Indirectly quoted exchange rate in an IDoc segment
internal data type : CHAR
Internal length : 000012 characters
Position in segment : 032, Offset : 0408. external length : 000012
E1EDK14 : IDoc: Document Header Organizational Data
Segment definition E2EDK14 Released since Release 30A , Segment length: 0038
QUALF : IDOC qualifer organization
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
ORGID : IDOC organization
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
E1EDK03 : IDoc: Document header date segment
Segment definition E2EDK03 Released since Release 30A , Segment length: 0017
IDDAT : Qualifier for IDOC date segment
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
DATUM : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 002, Offset : 0066. external length : 000008
UZEIT : IDOC: Time
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 003, Offset : 0074. external length : 000006
E1EDK04 : IDoc: Document header taxes
Segment definition E2EDK04001 Released since Release 40B , Segment length: 0107
MWSKZ : VAT indicator
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 001, Offset : 0063. external length : 000007
MSATZ : VAT rate
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 002, Offset : 0070. external length : 000017
MWSBT : Value added tax amount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 003, Offset : 0087. external length : 000018
TXJCD : Tax Jurisdiction
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 004, Offset : 0105. external length : 000015
KTEXT : Text Field
internal data type : CHAR
Internal length : 000050 characters
Position in segment : 005, Offset : 0120. external length : 000050
E1EDK05 : IDoc: Document header conditions
Segment definition E2EDK05001 Released since Release 40A , Segment length: 0185
ALCKZ : Surcharge or discount indicator
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
KSCHL : Condition type (coded)
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 002, Offset : 0066. external length : 000004
KOTXT : Condition text
internal data type : CHAR
Internal length : 000080 characters
Position in segment : 003, Offset : 0070. external length : 000080
BETRG : Fixed surcharge/discount on total gross
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 004, Offset : 0150. external length : 000018
KPERC : Condition percentage rate
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 005, Offset : 0168. external length : 000008
KRATE : Condition record per unit
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 006, Offset : 0176. external length : 000015
UPRBS : Price unit
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 007, Offset : 0191. external length : 000009
MEAUN : Unit of measurement
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 008, Offset : 0200. external length : 000003
KOBTR : IDoc condition end amount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 009, Offset : 0203. external length : 000018
MWSKZ : VAT indicator
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 010, Offset : 0221. external length : 000007
MSATZ : VAT rate
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 011, Offset : 0228. external length : 000017
KOEIN : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 012, Offset : 0245. external length : 000003
E1EDKA1 : IDoc: Document Header Partner Information
Segment definition E2EDKA1003 Released since Release 45A , Segment length: 0995
PARVW : Partner function (e.g. sold-to party, ship-to party, ...)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
PARTN : Partner number
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 002, Offset : 0066. external length : 000017
LIFNR : Vendor number at customer location
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 003, Offset : 0083. external length : 000017
NAME1 : Name 1
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 004, Offset : 0100. external length : 000035
NAME2 : Name 2
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 005, Offset : 0135. external length : 000035
NAME3 : Name 3
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 006, Offset : 0170. external length : 000035
NAME4 : Name 4
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 007, Offset : 0205. external length : 000035
STRAS : Street and house number 1
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 008, Offset : 0240. external length : 000035
STRS2 : Street and house number 2
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 009, Offset : 0275. external length : 000035
PFACH : PO Box
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 010, Offset : 0310. external length : 000035
ORT01 : City
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 011, Offset : 0345. external length : 000035
COUNC : County code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 012, Offset : 0380. external length : 000009
PSTLZ : Postal code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 013, Offset : 0389. external length : 000009
PSTL2 : P.O. Box postal code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 014, Offset : 0398. external length : 000009
LAND1 : Country Key
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 015, Offset : 0407. external length : 000003
ABLAD : Unloading Point
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 016, Offset : 0410. external length : 000035
PERNR : Contact person's personnel number
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 017, Offset : 0445. external length : 000030
PARNR : Contact person's number (not personnel number)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 018, Offset : 0475. external length : 000030
TELF1 : 1st telephone number of contact person
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 019, Offset : 0505. external length : 000025
TELF2 : 2nd telephone number of contact person
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 020, Offset : 0530. external length : 000025
TELBX : Telebox number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 021, Offset : 0555. external length : 000025
TELFX : Fax number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 022, Offset : 0580. external length : 000025
TELTX : Teletex number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 023, Offset : 0605. external length : 000025
TELX1 : Telex number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 024, Offset : 0630. external length : 000025
SPRAS : Language key
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 025, Offset : 0655. external length : 000001
ANRED : Form of Address
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 026, Offset : 0656. external length : 000015
ORT02 : District
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 027, Offset : 0671. external length : 000035
HAUSN : House number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 028, Offset : 0706. external length : 000006
STOCK : Floor
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 029, Offset : 0712. external length : 000006
REGIO : Region
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 030, Offset : 0718. external length : 000003
PARGE : Partner's gender
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 031, Offset : 0721. external length : 000001
ISOAL : Country ISO code
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 032, Offset : 0722. external length : 000002
ISONU : Country ISO code
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 033, Offset : 0724. external length : 000002
FCODE : Company key (France)
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 034, Offset : 0726. external length : 000020
IHREZ : Your reference (Partner)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 035, Offset : 0746. external length : 000030
BNAME : IDoc user name
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 036, Offset : 0776. external length : 000035
PAORG : IDOC organization code
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 037, Offset : 0811. external length : 000030
ORGTX : IDoc organization code text
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 038, Offset : 0841. external length : 000035
PAGRU : IDoc group code
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 039, Offset : 0876. external length : 000030
KNREF : Customer description of partner (plant, storage location)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 040, Offset : 0906. external length : 000030
ILNNR : Character field, length 70
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 041, Offset : 0936. external length : 000070
PFORT : PO Box city
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 042, Offset : 1006. external length : 000035
SPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 043, Offset : 1041. external length : 000002
TITLE : Title
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 044, Offset : 1043. external length : 000015
E1EDKA3 : IDoc: Document Header Partner Information Additional Data
Segment definition E2EDKA3 Released since Release 30D , Segment length: 0073
QUALP : IDOC Partner identification (e.g.Dun&Bradstreet number)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
STDPN : Character field, length 70
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 002, Offset : 0066. external length : 000070
E1EDK02 : IDoc: Document header reference data
Segment definition E2EDK02 Released since Release 30A , Segment length: 0058
QUALF : IDOC qualifier reference document
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
BELNR : IDOC document number
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
POSNR : Item number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 003, Offset : 0101. external length : 000006
DATUM : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 004, Offset : 0107. external length : 000008
UZEIT : IDOC: Time
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 005, Offset : 0115. external length : 000006
E1EDK17 : IDoc: Document Header Terms of Delivery
Segment definition E2EDK17 Released since Release 30A , Segment length: 0076
QUALF : IDOC qualifier: Terms of delivery
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
LKOND : IDOC delivery condition code
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0066. external length : 000003
LKTEXT : IDOC delivery condition text
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 003, Offset : 0069. external length : 000070
E1EDK18 : IDoc: Document Header Terms of Payment
Segment definition E2EDK18 Released since Release 30A , Segment length: 0089
QUALF : IDOC qualifier: Terms of payment
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
TAGE : IDOC Number of days
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 002, Offset : 0066. external length : 000008
PRZNT : IDOC percentage for terms of payment
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 003, Offset : 0074. external length : 000008
ZTERM_TXT : Text line
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 004, Offset : 0082. external length : 000070
E1EDK35 : IDoc: Document Header Additional Data
Segment definition E2EDK35000 Released since Release 45A , Segment length: 0078
QUALZ : Qualifier for IDoc additional data
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
CUSADD : Data Element Type CHAR Length 35
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
CUSADD_BEZ : Character field of length 40
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 003, Offset : 0101. external length : 000040
E1EDK36 : IDOC: Doc.header payment cards
Segment definition E2EDK36000 Released since Release 45A , Segment length: 0114
CCINS : Payment cards: Card type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 001, Offset : 0063. external length : 000004
CCINS_BEZEI : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 002, Offset : 0067. external length : 000020
CCNUM : Payment cards: Card number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 003, Offset : 0087. external length : 000025
EXDATBI : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 004, Offset : 0112. external length : 000008
CCNAME : Payment cards: Name of cardholder
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 005, Offset : 0120. external length : 000040
FAKWR : Maximum amount
internal data type : CURR
Internal length : 000015 characters
000002 decimal places, without sign
Position in segment : 006, Offset : 0160. external length : 000017
E1EDKT1 : IDoc: Document Header Text Identification
Segment definition E2EDKT1002 Released since Release 45A , Segment length: 0089
TDID : Text ID
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 001, Offset : 0063. external length : 000004
TSSPRAS : Language Key
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0067. external length : 000003
TSSPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 003, Offset : 0070. external length : 000002
TDOBJECT : Texts: Application Object
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 004, Offset : 0072. external length : 000010
TDOBNAME : Name
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 005, Offset : 0082. external length : 000070
E1EDKT2 : IDoc: Document Header Texts
Segment definition E2EDKT2001 Released since Release 40A , Segment length: 0072
TDLINE : Text line
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 001, Offset : 0063. external length : 000070
TDFORMAT : Tag column
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 002, Offset : 0133. external length : 000002
E1EDP01 : IDoc: Document Item General Data
Segment definition E2EDP01007 Released since Release 640 , Segment length: 0542
POSEX : Item number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 001, Offset : 0063. external length : 000006
ACTION : Action code for the item
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0069. external length : 000003
PSTYP : Item Category
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 003, Offset : 0072. external length : 000001
KZABS : Flag: order acknowledgment required
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 004, Offset : 0073. external length : 000001
MENGE : Quantity
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 005, Offset : 0074. external length : 000015
MENEE : Unit of measure
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 006, Offset : 0089. external length : 000003
BMNG2 : Quantity in price unit
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 007, Offset : 0092. external length : 000015
PMENE : Price Unit of Measure
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 008, Offset : 0107. external length : 000003
ABFTZ : Agreed cumulative quantity
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 009, Offset : 0110. external length : 000007
VPREI : Price (net)
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 010, Offset : 0117. external length : 000015
PEINH : Price unit
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 011, Offset : 0132. external length : 000009
NETWR : Item value (net)
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 012, Offset : 0141. external length : 000018
ANETW : Absolute net value of item
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 013, Offset : 0159. external length : 000018
SKFBP : Amount qualifying for cash discount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 014, Offset : 0177. external length : 000018
NTGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 015, Offset : 0195. external length : 000018
GEWEI : Weight unit
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 016, Offset : 0213. external length : 000003
EINKZ : Flag: More than one schedule line for the item
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 017, Offset : 0216. external length : 000001
CURCY : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 018, Offset : 0217. external length : 000003
PREIS : Gross price
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 019, Offset : 0220. external length : 000018
MATKL : IDOC material class
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 020, Offset : 0238. external length : 000009
UEPOS : Higher-Level Item in BOM Structures
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 021, Offset : 0247. external length : 000006
GRKOR : Delivery group (items delivered together)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 022, Offset : 0253. external length : 000003
EVERS : Shipping instructions
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 023, Offset : 0256. external length : 000007
BPUMN : Denominator for Conv. of Order Price Unit into Order Unit
internal data type : DEC
Internal length : 000005 characters
No decimal places, without sign
Position in segment : 024, Offset : 0263. external length : 000006
BPUMZ : Numerator for Conversion of Order Price Unit into Order Unit
internal data type : DEC
Internal length : 000005 characters
No decimal places, without sign
Position in segment : 025, Offset : 0269. external length : 000006
ABGRU : Reason for rejection of quotations and sales orders
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 026, Offset : 0275. external length : 000002
ABGRT : Description
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 027, Offset : 0277. external length : 000040
ANTLF : Maximum number of partial deliveries allowed per item
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 028, Offset : 0317. external length : 000001
FIXMG : Delivery date and quantity fixed
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 029, Offset : 0318. external length : 000001
KZAZU : Order Combination Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 030, Offset : 0319. external length : 000001
BRGEW : Total weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 031, Offset : 0320. external length : 000018 -
Idoc Segment Cancel release error
Hi all,
I have problem in cancelling the release of an Idoc Segment. I have a requirement to add new fields to the segment. When I try to do Edit->Cancel Release it is throwing below error.
"Error while resetting release of segment Z1PXXXX
Message no. EA259"
Could anyone tell me how to overcome this error or the root cause of this error?
Many Thanks,
Sri
Edited by: Arunsri on Nov 10, 2009 8:37 AMHello,
The reason that you are getting these errors is that you cannot cancel
the release of an extension made in previous version e.g. 4.6C. Instead you have to
create a new extension.
It is not possible to change a segment definition which is released in a
lower release. This is a basic concept of our release strategy to
guarantee compatibility between different releases.
You must create a new segment definition for the new release e.g. 620 with a new segment
field with the appropriate length. In transaction WE20, outbound parameters, you can specify
the "segment release in IDoc type" for the communication. Please read the F1 help of this field for further
information.
For your own segments you can define a new version of the segment via
transaction WE31 -> Add Version (Shift+F5).
Please review your online help for more information on this and related topics.
Hope this information helps.
Regards,
David -
Problem in file content conversion from XML to CSV
Hi Experts,
I am finding problem in file content conversion. I need to convert the following XML file into CSV file:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_CROSS_REF xmlns:ns0="urn:dabur:idoc2file:pos">
<Update_type>2</Update_type>
<PLU>00000000</PLU>
<Cross_ref_PLU>7777777</Cross_ref_PLU>
<Capture_PLU />
<Package_size />
<Package_desc />
</ns0:MT_CROSS_REF>
The output file data has to be like:
2,00000000,7777777,,,,
The problem I am facing is while specifying the content conversion parameters in communication channel i dont know what recordset structure i should mention as all the records are directly under root. If I mention recordset structure as "ns0:MT_CROSS_REF" and parameters as
ns0:MT_CROSS_REF.fieldSeparator ,
ns0:MT_CROSS_REF.endSeparator 'nl'
i get error in communication channel monitoring and no file is posted.
Please help me as to what correct parameter i should mention in my case.
Thanks,
Regards,
YashHi Chirag,
I cannot change the xml file as it comes after mapping idoc to a message type. How can I add ROOT in the xml? My message type is like MT_CROSS_REF and it has those 6 fields as in the XML (Update_type, PLU etc.). I do the mapping of these fields from a IDOC and get the XML.
I hope you got my point.
Thanks,
Yash -
IDOC Segment Adding a new field
Hi all!
My disclaimer: I know less than nothing about IDOCs. So hopefully I lead you down the right path. I have searched SDN and then tried google. As far as I can tell I've gone thru the right steps. But since it isn't working I must have skipped a step.
Here's what I've done:
1. Changed the segment via WE31. I had to cancel the activation. So I activated it again. It did generate a change request.
2. Updated the custom function module. Hard coded a value into that field just to see if it would work.
Tested it by running the invoice transaction. I see the IDOC with all the fields except for the one I added.
Next:
1. Cancel the activation on WE31.
2. Cancel the activation for the Object via WE30.
3. Activate the segment via WE31.
4. Activate the object via WE30.
5. Verify the structure was correct via SE11.
All looked good, I tested again. Again the IDOC was generated with all the fields except for the one I added.
I've since tried some other things. That do not really make a lot of sense, but I tried them. Does anyone know what I'm missing? How do I get the new field to display on my IDOC?
(I've also checked the partner profile via WE20 and verified the message type and object...)
Thank you!
Michelle1. you have to activate WE30/WE31
2. you have to maintain your IDoc & extension in the WE20 outbound parameters.
3. you have to create a CMOD Project to activate your customer Exit for Incoice IDocs
4. you have to fill the new z-field with relevant value in the Function Module "assigned in CMOD".
if all steps are done. Put a breakpoint in the module to see that the z-field is filled.
Regards,
Gordon -
Facing Problem in IDOC to EDI FLAT File Scenario
Hi,
I am working on a scenario IDOC to EDI FLAT File. For this I have used ABAP mapping.
The problem i am facing is that the EDI FILE contains the segment name as E1EDK01 for eg. while I need the name as per the latest segment definiton released. I have also tried this using File port and it gives the required segment names in file. But we dont have to use File ports. Please suggest me if something is missing in PI Abap stack ?? Why I am not getting the segments name as per latest segment definition mainatined in R3.
Thanks
NehaHi Neha,
Please check the segment name in sxmb_moni. Is this showing new value or the old value?
If SXMB_MONI shows old value then the source SAP (R/3) system which is sending the idoc may not have released the segment after changing the name. You need to ensure that the idoc segment has been released properly. Then re-import the iodc into PI server again. Finally delete entry of the iodc structure in idx2 transaction, no need to re-import the idoc structute again in idx2, since once you run the scenario the metadata automatically gets imported.
regards
Anupam -
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 PMHi 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.
Maybe you are looking for
-
Don't know how to add any more details.
-
Download option is not working
my nokia x6 00 ,in Nokia Store option ..download option is not working Moderator's note: We have provided a subject-related title to help other forum users easily view and respond to this post.
-
Function key and moving the columns in a table
Hi all, Can anyone help me how to make use of function key UI element in nwds 7.1 ehp1 version.. and also how to move the columns of the tables at run time... thanks, viswa
-
Image Quality Difference Among File Formats.
I'm creating a title sequence in After Effects that uses a series of still images. I've been using TIFF formatted images and was pleased with the quality. On the other hand, I've started to try to use Photoshop EPS images because it's easy to create
-
System recovery fails on Satellite A30
Im trying to restore my gfriends laptop form the disks supplied. I get about 5% and it fails lots of writing happens the highlights of which are below: Error number: (36000) Message: A General Exception occured Version: 7.00 Command line arguments: -