IDOC - segment Qualifier
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éronique
Hi 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
Similar Messages
-
IDOC SEGMENT QUALIFIER DOUBT...
Gurus,
I was looking at a givcen IDOC which was posted. The IDOC was of t5ype INVOIC01. I see that there are couple of segments with the same name but with different IDOC qualifier like:
EIEDP02 which has three qulaifier reocrds like 001, 002 and 016. But the data gets posted only from one of this qualifier record.
What is a qualifier ? How the system comes to know what qualifier record should be used to post data?
Regards,
Rajesh.>What is a qualifier ? How the system comes to know what qualifier record should be used to post data?
if it is inbound it should be handled by Inbound processing function module. if it is Outbound then a predefined mapping (Requirement specific) can tell you which qualifier belongs to what data.
and also Read the Idoc type documentation using tcode WE61. -
Is there a way to find out the segement qualifier definition in SAP system? Like
int_edidd-segnam = 'E1EDK02'.
IF ekko-bstyp = 'A'.
e1edk02-qualf = '003'.
ELSE.
e1edk02-qualf = '001'.
ENDIF.
When to use '003 and '001'.
Many idoc segement carrier different qualifiers codes...
Thanks
AlokHi,
You can find them in Idoc documtation of WE60 transatcion.
You can also find them by going to domian of the particaular idoc field and looking at
the 'Fixed values'.
Regards,
Shan -
Read IDOC segment with qualifier
Hi,
I need to read data into a workArea from a IDOC segment which has Qualifiers for it.
The IDOC or BASIC type is DELVRY03.
Segment E1EDT13.
Qualifier 006
Thx in advance
MacDATA:
lx_e1edt13 TYPE e1edt13.
FIELD-SYMBOLS:
<fs_idoc_data> LIKE LINE OF idoc_data.
LOOP AT idoc_data ASSIGNING <fs_idoc_data> WHERE segnam = 'E1EDT13'.
lx_e1edt13 = <ls_idoc_data>-sdata.
IF lx_e1edt13-qualf = '006'.
your code
or get the data into internal table as per your requiremnt
ENDIF.
ENDLOOP. -
Hi,
I just want to know how I can get all the qualifers in all the segments in an iDoc as well as display all the valid value ranges for the qualifiers.
I know I can get to the domain for a specific segment qualifier and display the value range in se11 but what I want is to be able to specify an iDoc and return a list of all qualifiers in segments and their value ranges.
Is there a function module that can handle this or possibly an ABAP program?
For example, I want all the qualifiers in Basic Type iDoc SHPMNT03.
Thanks in advance for any help.Hi,
Use SAP Standard IDOC Display Functionality for this:
From the R/3 initial screen choose Tools -> Business Communication -> IDoc -> IDoc Basis
In the Tree Control Display ..refer to Data Records....and you will see the Qualifier Info, if any....
Use Given below Link:
http://help.sap.com/saphelp_di46c2/helpdata/EN/dc/6b81ac43d711d1893e0000e8323c4f/frameset.htm
and see the Data Records Section. -
Hi,
Iam new to idocs and a functional consultant. I need to know whenever we receive the inbound idocs and if i see the segments of the inbound idoc, do the fields which i see in the segments are the sap fields.????/ for instance if the inbound idoc needs to create a sales order, then the fields of the segments of such an inbound idoc are the normal sap sales order fields ??
do i need to give functional specs to the abapers that whenever the inbound idocs is received the segments fields need to be mapped to sales order fields if such an idoc needs to create a sales order ??
regards
sachinHi Sachin,
Most of the IDoc segment fields are simmilar to SAP transaction fields e.g. most of the ORDERS IDoc segment fields will be simmilar to what you can see in VA01/VA02 screen fields.
Some fields may have different names.
In the case of few segments which may repeate in IDoc with different qualifiers (such as partner details, date segments), fields will be same but different qualifier value decides where these field values will be populated in the Order.
If you are using standard function module to create Order, it will take care of mapping IDoc segment fields to VA01/VA02 screen fields. But if it is a Z function module, then you need to specify the mapping.
Hope this information will help you.
Regards,
Mahesh Pakhale -
Hi,
I am using ORDERS04 as basic type for order creation from iDOC.
For one of my requirment I need the iDOC segment for VBKD-BSTKD_E field. The field is in purchase order data at header > Ship to party view > Purchase order no.
Thanks
SanjayHi,
you have to fill the segment E1EDK02 with:
E1EDK02-QUALF (qualifier) = '044' (purchase order number consignee)
E1EDK02-BELNR = Purchase Order Number
E1EDk02-DATUM = Purchase Order Date
Kind Regards.
Andrea -
Hi,
How can i change the field attached to a IDOC segment.
Actually we have this Invoice IDOC,in which the E1EDK03 012(Qualifier) is passing the IDOC creation date instead of Billing date.
So i need to change this mapping to Billing date.
Please help.Hi Salz,
I just checked my version of SAP (4.7) and you should get an invoice date. Check out the subroutine FILL_E1EDK03 in function module IDOC_OUTPUT_INVOIC. The first section of this code creates an E1EDK03 segment with the invoice date (if there is an invoice date), with qualifyer 026.
Is there a possibility that in fact you are getting an E1EDK03 segment with the invoice date, but you are also getting other E1EDK03 segments (such as the one you mention with qualifyer 012) and they are obscuring the one you are looking for?
If there are definitely none being created then can I suggest that you debug the subroutine FILL_E1EDK03 in function module IDOC_OUTPUT_INVOIC to check what is happening. You may need to change the timing of your output record to 1 and run the program RSNAST00 online to get the breakpoint to be hit correctly.
If, in your version, the code doesn't include this date, then you have an exit function module EXIT_SAPLVEDF_002 (called via the subroutine CUSTOMER_FUNCTION in function module IDOC_OUTPUT_INVOIC) where you can actually add your own segment data. For example you an change the contents of an existing segment (as per your original request), or append your own E1EDK03 segment with your own data. I would recommend adding your own segment rather than changing whats there.
It is possible to extend idocs to add your own custom segments (eg Z1EDK03), but I wouldn't recommend it in your case, because in later versions of SAP the date is provided and by not creating a new segment (Z1EDK03) you will have no mapping changes to do when you upgrade. You can just delete your userexit code.
Hope that all makes sense and helps you with your problem.
Cheers,
Brad -
How to pass item payment term through Idoc segment E1EDP18
We use ORDERS idoc to create sales orders and our customers want to replace the default payment term at item level. I found segment E1EDP18 for this purpose but I don't exactly know how to use it, like where to put the payment term key. Can any one expain with the help of a clear example how to indicate the payment term there ?
Below is a exerpt of the incoming idoc file I used for testing. In this test I put the paymentt term 0010 in but the information sent in idoc segment is just ignored.
E1EDP01 10 625.00
E1EDP05 ZD64
E1EDP05 ZD66
E1EDP19 00269020000
E1EDP18 0020010
Many thanksHi,
SAP program IDOC_INPUT_ORDERS is not using the item level payment terms sent in IDOC segment P18 to fill the sales order so you need user exit to do this. The program is moving the item level information to an internal table xe1edp18 when the data is parsed from IDOC so you can use this to populate the screen information in the user exit 'CALL CUSTOMER-FUNCTION '002' (IDOC_INPUT_ORDERS).
Let me explain the process from EDI to SAP.
1) EDI 850 will have ITD segment at item level (Example ITD013 *2 * *10 * *30 * * *) you can ask your EDI team to map them to P18 segment as it has the number of days and also the percentage for cash discount. P18 has 3 qualifiers so you can map 3 different temrs (For example the above sample is 1 Term is 2% in 10 days and Term 2 is net 30 days)
2) During IDOC parsing the program is already filling internal table xe1edp18.
3) In the user exit CUSTOMER-FUNCTION '002' you need to search for the SAP payment terms with the number of days and percentage (This is available in the table T052). Once you find the SAP terms key, you need to populate it for each item. You need to do this after the program filled the item billing data.
Dynpro item business data billin details -
PERFORM VA01_DYNPRO_POSITION_PDE3 USING XVBAP-POSNR.
*-Zusätzliche Daten für Dynpros vorsehen (Kundenerweiterungen)----
*-additional data's for new dynpro fields (customer exit)----
SY-SUBRC = 0.
PERFORM CUSTOMER_FUNCTION_DYNPRO. -- THis is the user exit call
Hope this is useful.
Ram -
IDOC segment report with domain lookup
Does anyone know of a report that will list an IDOC's segments with the qualifier texts expanded.
Example:
The E1EDK14-QUALF segment belongs to domain EDI_QUALFO (IDOC qualifier organization) which has 19 values in its value table.
I'd like a report that would print the IDOC segment by segment along with the qualifiers value text.Hello Ed,
Use function module 'IDOCTYPE_READ_COMPLETE'. This will give you a list of segments with description, a list of fields with description, a list of domain values for the fields and a list of message types connected to that IDOC type.
You need to populate PI_IDOCTYP with the IDOC type and possibly PI_CIMTYP with the extension, if you are using an extension with that type. If not, Idoc Type is sufficient.
Regards,
Michael -
Idoc segment for updating Sales order item dates
Hi All,
I would ike to update the sales order item dates (loading date, Goods Issuance date etc) from an IDOC.
please let me know the Idoc segment and fields that need to be filled in?
Thanks in advance.
Regards,
Zeeshan.Hi,
Here are some details of the segments in the idocs -
SEGNAM Segment Name E1EDL20
VBELN Sales and Distribution Documen 180001539
SEGNAM Segment Name E1EDL18
QUALF IDOC Qualifier: Control (Deliv PIC : Picking with flow records (inbound)
SEGNAM Segment Name E1EDL18
QUALF IDOC Qualifier: Control (Deliv PGI : Post delivery goods issue (inbound)
SEGNAM Segment Name E1EDT13
QUALF IDOC Qualifier: Date (Delivery 010 : Picking
NTANF Constraint for activity start 20090808
ISDD Actual start: Execution (date) 20090808
SEGNAM Segment Name E1EDL24
POSNR Item number of the SD document 10
MATNR Material Number 1112
WERKS Plant SG01
KDMAT Material belonging to the cust 1112
LFIMG Actual quantity delivered (in 55
VRKME Sales unit EA
POSEX External item number 10
ORMNG Original Quantity of Delivery 55
SEGNAM Segment Name E1EDL41
QUALI Qualifier for Reference Data o 001 : Purchase order data of customer
BSTNR Customer purchase order number 4500004668
BSTDT Customer purchase order date 10
POSEX Item Number of the Underlying 10
SEGNAM Segment Name E1EDL37
Regards,
Shamma -
Replaced value is not getting relected in IDOC segment field
Hi,
Need your help for the below issue.
I am replacing the PO # with Delivery Doc # . But the replaced value is not getting reflected in the IDOC segment field(e1bp2017_gm_item_create-po_number.).
Function Module which I am using is IDOC_INPUT_MBGMCR as a copy.
Here is my code given below:
SELECT
SINGLE vbeln
INTO lx_vbeln
FROM lips
WHERE vgbel EQ e1bp2017_gm_item_create-po_number.
Move lx_vbeln TO e1bp2017_gm_item_create-po_number.
MOVE-CORRESPONDING e1bp2017_gm_item_create
TO goodsmvt_item.
Then this is passed as TABLE in "BAPI_GOODSMVT_CREATE".
Please do the needful.Hi Dheepa,
Check it in debug whether the filed is empty or having po#, when ur code is executed for the replacement. if it is empty, po# is populated after ur code. in this case you need to write the code in suitable place.
Reddy -
Unable to change the length of field in idoc segment
Dear all,
My requirement is to change the length of a field(Z field) in a segment (Z Segment). I tried the following but in vain
1)Tried to Cancel the release and then change the length of the domain. Unfortunately it is givin an error saying "Error while resetting release of segment ZC9DEMARA01".
I also tried cancelling hte release of extension and then cancelled the release of segment
2) Created a new version, but in new version the earlier fields are diabled. So I am unable to edit.
I have gone through some of the links available in SDN but I could not solve as I am unable to cancel the release in the first step.
[Idoc segment field length changes]
Could you please help me.
Thanks in advance!
regards,
AravindHello Aravind,
I Have created one Segment type with some fields, changed the field length also its working.
just try to cancel the release and change the length of the filed and do it set release again.
Try it .
Thanks,
santhosh -
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 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!
Maybe you are looking for
-
Special stock partner data problem in ERP system during "Post Goods issue"
Hi all, I have a (probably) customizing issue in an ERP 6.0 EhP4 test system which not occurs in the ERP 6.0 test system. There is a difference but no one could tell me, what causes the problem in this scenario: I have two customers, C1 and C2. C2 is
-
I tried to reset then i removed caches/cookies but nothing worked. I am having this problem with plugins like Adobe Shockwave Flash and Java(TM) Platform SE 7 U72 . It seems that Firefox can't remember my settings. That red icon on left side of addre
-
Hi folks, I have a G4 Tower with OS 10.4.3 and 2 harddisks and spotlight just stopped working. Trying to include/exclude from the privacy folder didn't help and spotless (1.0.3) just doesn't work. Unfortunately I'm not experienced in using the termin
-
Would you recommend an imac 27" or a Macbook Pro 15" retina display?
Portability does not matter at all in this case. Would you recommend buying a Macbook pro 15" or an imac 27". Can you list some pro's and con's? Thank you very much!
-
Cloud Dashboard not installing in Labview 2014
Hi guys, I'm trying to use Cloud Dashboard with LabVIEW 2014. I'm following https://decibel.ni.com/content/docs/DOC-38359 but the attachement at the bottom of the instructions does not open in VIPM Labview Tools Network. Instead I get the general