IDoc qualifier
Hi All,
We are using IDoc type DELVRY05 for pick confirmation of the outbound delivery. We want required quantity to be changed as per the pick quantity and PGI to be done automatically. For this we are using qualifier PIC and PGI respectively. But what value needs to be maintained as a parameter to this qualifier.
We are getting error as PIC and PGI are not valid. Can any one help in resolving this problem.
Regards
Prashant
Message was edited by:
Prashant Anant Tawde
Hi ,
I am also Facing the same problem i am able to pass the reference value for ship to party using Qualifier 044..but not able to pass the value for sold to party..
please help me if u got the solution in your case..
Regards
-Arun
Similar Messages
-
Idoc qualifier for field ihrez segment e1edp02
Hi all,
I am using field ihrez of segment e1edp02 twice for posting the reference ( ship to ref and sold to ref)...I could find the idoc qualifier for ship to reference is 44 ..what can i use for sold to reference.. can somebody help me with this please.
Thanks,
Kiran..Hi ,
I am also Facing the same problem i am able to pass the reference value for ship to party using Qualifier 044..but not able to pass the value for sold to party..
please help me if u got the solution in your case..
Regards
-Arun -
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 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. -
Creating Sales Orders from Quantity Contract - ORDERS05 IDOC
Hi,
I have created a Quantity Contract in ECC. Now I want sales orders to be created w.r.t to the Contract through ORDERS05.
Can anyone suggest which IDOC Segment and Qualf i have to populate to achive the same.
Also say once I am able to achive the creation of Release Orders from the Contract through ORDERS05. If I surpass the Qty of the Contract . The IDOC should be have a field for notifying the same.
REgards,
BInayakHello Binayak
You may use the following segment and fields for reference data:
Segment: E2EDK02
Fields:
QUALF : IDOC qualifier reference document - I think for contracts this is '001'.
BELNR : IDOC document number
POSNR : Item number
As per a flag to indicate that the contract quantity is surpassed, I doubt there will be anything like that becasue is an Idoc is before you created the order and how will the system know you have surpassed until an order is entered?
I think you need to use 'completion rule' and copy control 'update document flow' features to work on this.
Hope this helps. -
Delete non-picked items in delivery using iDoc
Hello gurus,
I'm integrating SAP ECC and external WM solutions using iDocs. The outbound delivery is created in SAP ECC and sent to WMS using DESADV iDoc. The picking is performed in WMS and the list of shipped items with batch numbers are returned to SAP and Goods Issue is posted. iDoc WHSCON is supposed to be used for that purpose.
The problem is that in case if not all the line items were shipped it's necessary to delete them from the delivery because otherwise GI will not be posted. But the non-picked items no longer exist in the response iDoc WHSCON so it's even impossible to set QUALF=DEL for these items. WMS sends back only actually shipped items in iDoc, and not the deleted ones.
Do you have any solutions for overcoming this problem?
Maybe there is any BAPI or iDoc qualifier that will allow to delete all items from the delivery so that they will be recreated by the same iDoc? Or there is any checkbox in SAP that will automatically delete unpicked items during posting of GI?
Thanks!hi
in this both error comes ,
1)E VL 609 20 Delivery has not yet been put away / picked (completely)
a) picking quantity not entered , in delivery , first you enter the picking quantity ,
you create the 2 lines for sale order , so create for one line item for delery , go to vlo1n enter shipping point , sale order number line item number 1 to 1 enter press enter system will take only one item in delivery then you enter the picking quantity , and pgi ,
in delivery two line item only line item enter picking quantity and another line item not enter the picking quantity , it not possible to pgi , both line item you enter the picking quantity ,
you create the same delivery number for 2line item , so first complete the 1st line item pgi and , go to vl02n and enter , click on menu bar out bound deliverrs-delivery sale order -enter sale order number and line item , and do the pgi ,
2)VL 608 20 Delivery has not yet been completely processed by WM
you process activate the wm , so you can do the lt03 , then it will come vlo2n and check the picking quantity it will come auto matically -
LSMW & IDOC - Multiple Constants in the Same Target Field
Hi,
I'm trying to create sales orders by using the IDOC ORDERS05 starting from a LSMW.
The only problem we have right now is that all Org Data in the IDOC is stored in a structure [E1EDK14 IDoc: Document Header Organizational Data] that contains two fields and need to be duplicated with different values.
I've been able to load from file with a Source Structure Hierarchy but since the 3 entries I want to make are always the same for all Sales Orders, I was wondering if I could do it within LSMW without the need to have data in a external file.
So Basically, I need for every header these 3 entries :
Structure E1EDK14
QUALF - IDOC Qualifier | ORGID - IDOC Organization
008 | 0010
006 | 99
007 | 99
Is there any way of doing this without development ?
Thanks in advance !Yes you're right, I found it :
Put this in the __END_OF_RECORD__ section.
*Sales Organization
E1EDK14-QUALF = '008'.
E1EDK14-ORGID = '6720'.
transfer_record.
*Sales Division
E1EDK14-QUALF = '006'.
E1EDK14-ORGID = '99'.
transfer_record.
*Distribution Channel
E1EDK14-QUALF = '0007'.
E1EDK14-ORGID = '99'.
transfer_record. -
Hii...experts...
I am new to the topologies IDOC,ALE and RFC connection...my requirment is when I create a sales order in one client (say) development..I want to create that sales order in another client (say) quality automatically, for this i want to create and trigger IDOC automatically..whether it is possible? if yes,can u plz give me the steps..
helpful answers will be rewarded..
Thanks Sugumar.GHi,
Salesorder IDOC
In this example a purchase is created, using the SAP standard functionallity for creating salesorders. When the salesorder is saved, and IDOC is automatically generated. Then we use the IDOC test tool to
create an order confirmation from the salesorder IDOC.
Create Vendor
Create customer
Create partner profiles
Create purchase order
Create the order confirmation IDOC
Create vendor
Create vendor using transaction code MK01. You can also use an existing vendor.
Vendor: T-BILHFN
Purch. org. : 001
Purchase organization may vary from system to system.
Create Customer
Create a customer using transaction VD01. You could also use an existing customer.
In the follwing example the vendor 3471 is used.
Create partner profiles
Create vendor partner profile
General data
Out bound parameters
Inbound parameters
Create customer partner profile
General data
Outbound parameters
Imbound parameters
Create purchase order
Use transaction ME21 to create the purchase order
To send an IDOC when the document is finished, go to Header -> Messages and
change the output medium to EDI.
Then select Further Data and change Dispatch Time to Send immediately. This will
create the IDOC as soon as the purchase order is saved.
Save the document.
Use transaction WE02 to check that the IDOC has been created without errors
Create the order confirmation IDOC
As the system has not been configured to handle the IDOC flow, the IDOC test tool
is used to simulate the flow. The Order IDOC is used as a template to create the
order confirmation IDOC.
Transaction code: WE19
Type the number of the Order IDOC in on the start screen and select menu IDOC ->
Create to create the template.
Change the control record
Note that the name of the port SAPTST may vary from system to system. The name can be seen in the Sender
port of the IDOC
Create new E1DK02 segment
The E1DK02 Document header reference data segment includes references to other documents.
The new E1DK02 segment should be created as a copy of the existing E1DK02, and at the same level.
Change the following fields of the record:
Qualifier: 002
Document item: 10
Qualifier = IDOC qualifier reference document = 002 = Vendor order
Document item =: Item number, see the item number on the purchasing document
Create E1EDP02 segment
The E1EDP02 Document Item Reference data includes references to other documents.
Create E1EDP02 as subelement of E1EDP01 Document item General Data
Qualifier: 001
Document: 4500010757
Document item: 10
Qualifier : IDOC qualifier reference document 001 = Customer purchase order
Document : Document number The number of the purchase order
Document item : Item number, see the item number on the purchasing document
Changing the ACTION field at header or item level
If you are working without a confirmation control key, the IDoc must have a processable action code at either
header or item level:
At header level, the segment field ACTION of segment E1EDK01 must be filled with the value '000' if the complete
purchase order is to be confirmed.
At item level, the segment field ACTION of segment E1EDP01 must be filled with the value '000' or '004' if the PO
item is to be confirmed.
Test IDOC
After the changes have been made, press the Standard Inbound button to generate the IDOC.
If no errors occurs go to transaction WE02 to check if the IDOC has been processed without errors.
If the IDOC has been processed without errors, then display the Purchase order (Transaction ME23). display the
item data and double-click on the item line. If all went well, you will now se that the field Acknowl. no. has been
filled out.
Pls. reward if useful.... -
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 -
IDoc_inptut_ordchg order item
Hi Gurus
how can i pass from xi item number of sales order. if i try to pass the value on e1edp01-posex the system is searching for the POitem,not for the item from salesorder. is there any possibilty to access with the right key?
thanks
RalphHi,
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 -
Purchase Order Number in Orders05
Hi,
I am looking for the PO Number in the Orders05 idoc type. The 2 segments that I am looking in are E1EDKA1 and E1EDP01. They do not exist in either of them. Any inputs will be appreciated.
regards
AveekAveek,
Go to Transaction code WE63 and give the message type ORDERS05 and execute, it will display the documentation for each segment.
PO number field is avaialbe in E1EDK02 segment with Qualifier as '001' and BELNR as the field for entering the PO number.
BEGIN_SEGMENT E2EDK02
SEGMENTTYPE E1EDK02
QUALIFIED
LEVEL 02
STATUS OPTIONAL
LOOPMIN 0000000001
LOOPMAX 0000000010
BEGIN_FIELDS
NAME QUALF
TEXT IDOC qualifier reference document
TYPE CHARACTER
LENGTH 000003
FIELD_POS 0001
BYTE_FIRST 000064
BYTE_LAST 000066
VALUE '001'
VALUE_TEXT Customer purchase order
Thanks
Giridhar -
How to Map Idoc-Orders05 Qualifier permitted values to a flat file Str
Hi All,
My scenario is IDoc-xi-flat file. I have a problem in mapping the respective qualifier value in IDoc to the flat file structure. I am using the function fix values in Message Mapping. Suggest how should the target field should look like to map to the qualifier.
Thanks
Gowri K.hi,
can you tell a little bit more on what are you trying to achive?
do you only need one qualifier in file or all or what?
can you use the same structure as in IDOC ?
be a little more precise
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a> -
How to map IDoc segment with qualifiers
Hi everyone!
I have the following problem: In an IDoc of type DESADV01 there can be several segments of type E2EDS01. Each segment has a different qualifier, which is the value of the field SUMID in this case. My target structure (type EDIFACT) now has several segments, each again with a sort of qualifier. Now I have to map the values of certain source segments to the respective target segments.
Exaple (in XML format):
Source
<E1EDS01 SEGMENT="1">
<SUMID>021</SUMID>
<SUMME>0000000001.000</SUMME>
<SUNIT>KGM</SUNIT>
</E1EDS01>
<E1EDS01 SEGMENT="1">
<SUMID>022</SUMID>
<SUMME>0000000001.000</SUMME>
<SUNIT>KGM</SUNIT>
</E1EDS01>
Target
<S_MEA>
<C_C502>
<D_6313>N</D_6313>
</C_C502>
<C_C174>
<D_6411>KGM</D_6411>
<D_6314>1</D_6314>
</C_C174>
</S_MEA>
<S_MEA>
<C_C502>
<D_6313>G</D_6313>
</C_C502>
<C_C174>
<D_6411>KGM</D_6411>
<D_6314>1</D_6314>
</C_C174>
</S_MEA>
(i have omitted several details here, but I'm only interested in the general procedure anyway).
So in general the source segment with qualifier "021" should be mapped to a target structure with qualifier "N" etc.
How can this be done using standard XI mapping techniques?
Regards, JoergHi everyone!
Thanks for your input data - unfortunately this wasn't quite what I was looking for. However I thik I solved my original problem and I just wanted to share this solution with you - maybe it helps others, maybe some of you have suggestions what I could do differently.
To sum up the requirement: There can be multiple input segments, each with a certain qualifier. These input segments have to be mapped to the target segments, respectively - however, the qualifiers change. There can be several segments with qualifiers that do not match the requirement, and required segments might be missing.
So here's what I came up with:
Use the qualifier of the source segments as an input to a <b>FixValues</b> function. In this function, map the desired qualifiers to the value <b>true</b>, use <b>false</b> as the default value. Map the output of the <b>FixValues</b> function to a <b>createIf</b> function and use this to create the desired output segment. This way, for each of the required segments, one target segment will be created. All other segments (with unwanted qualifiers) will be removed.
So far, this technique worked for me - do you have improvements/suggestions?
Regards, Joerg -
Idoc custom qualifier to pexr2002
Hi,
In a pexr2002 type idoc I'm trying to add E1IDB02 segment with a custom qualifier while generating the idoc in an exit(ZXF08U04).
There are couple of other entries existing for E1IDB02 and when i try to add another entry with the custom qualifier , the Idoc errors out (error during syntax check).
Any hints are appreciated.
Thanks.
vk.Hello,
Lets say in DELVRY05 Idoc Type, we have a Segment Called E1EDL20 and since this is a Standard SAP Provided Basic Type, it will not have any Custom Segments ( Z-Segments). Now, If I want some additional Information to be populated as part of a Custom Segment, what I would do is to Create an IDoc Extension ZDELVRY05 with reference to the Basic Type DELVRY05 and Create a Custom Segment Z1EDL20 (Per Say) in which I'll populate the Custom Data Fields using an Exit. So, unless we create an IDoc Extension for a Basic Type, the Standard SAP Basic Type will not have any Custom Segments-Fields (Z-Segments).
Thanks,
Venkata Phani Prasad K
Maybe you are looking for
-
Vendor Invoices/Customer -BAPI
Hi all Equivalnt bapis to postVendor Invoices/Customer Invoices through f-02 transaction. we need to post with and without special GL Indicator. Can anyone let me knw which is the suitable bapi with SAMPLE DATA and MANDATORY FIELDS. Thanks sha
-
HELP!! Process exited with exit code 128.
Hi all, I am using JDeveloper 10G to develop a struts project. I use the struts-tiles.tld to construct the layout. <tiles:insert page="classicLayout.jsp" flush="true"> <tiles:put name="title" value="User and Assigned Role" /> <tiles:put name="header"
-
Can't receive faxes on LaserJet Pro MFP M225dw, but I can send with no problem
My new LaserJet Pro M225dw can send faxes but not receive. I have seen other posts on this forum regarding this issue but none of the answers have resolved my issue. I am copying the questions the responder in other posts has asked. What type of conn
-
I have 4665 songs on my iPod and am trying to organise them a bit better for ease of listening to what I want when I want, especially in the car. To facilitate this I've been creating Smart Playlists in iTunes to group songs into the categories I wan
-
Can any phone type be emulated in Device Central?
I'm just starting out on Mobile App development, and I'm trying to make sense of it all. To test the application process, I created a very simple Flash file, 550x400 pixels. One button click changes from one frame to another and moves some text on s