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
Similar Messages
-
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 Custom Fields are not coming in MII
Hi Guys,
I am receiving Standard IDOC (MATMAS) with Custom segment. Custom segment having two Z-fields and One Standard field. While fetching the IDOC at MII end, I am able receive IDOC except Z-fields, Custom Segment is coming perfectly with the one Standard field but missing Zfields.
I'm using MII 12.1.5 Build(92). Please provide your suggestions on this issue.
Thanks!Check if your MII is capbale of reciving the custom fileds. check mapping on sender and reciver side if z fileds are mapped correctly.
Check and evert,
Santosh Sarda -
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> -
JDBC to IDoc (Custom inbound function module)
Hi,
In my scenario JDBC to IDoc, I am using a custom function module to change the planned order. When I exectue the function module in WE19, it works fine and the IDoc status is also updated correctly.
But when I execute the entire interface right from JDBC, the status of the IDoc is set to 51 and the description it is giving is "No status record was passed to ALE by the application".
Can any one help me with this, where exactly is the error?For IDOC status 51 : Inbound IDOC
In WE19, Give the IDOC number & execute ... then put the cursor on the idoc control record . then click on the Standard Inbound push button on the application tool bar.it will show show all the details like partner no,type , message type , process code & function module name ...
now put a break point in the function module .. & debug .
if u r using customised inbound function module , then click on inbound function module .. there u will get a pop screen with FM name & debugging option in both background & foreground mode... -
ALE/IDOC[custom table transfer]
Hi All,
I have a doubt regarding the type of programs used to post the idocs using ALE in the outbound process.
Please also tell me which program I will use to post a custom table of mine to another server using ALE/IDOC.
Please also tell me the procedure to do the same mentioned above.
Please help. Its a urgent requirement...........................
Thanks in advance......................................................Hi Guru,
if you cannot use a standard idoc then you´ll need to create a custom one starting from the segment (WE31) where you can create an Idoc segment starting from your own Z table structure using the wizard.
Then you´ll need to also create the idoc type (WE30) and link the segment to the IDoc.
Then you´ll need to create a message type and link the message type to the Idoc type (WE81, WE82).
Then you´´ll use RFC "MASTER_IDOC_DISTRIBUTE" to populate the IDOC and send the data.
This is a sample code just to give you an idea:
DATA:
Z_SEGNAME(7) TYPE C VALUE 'SEGMENT',
Z_MESTYPE(9) TYPE C VALUE 'MESSAGE',
Z_IDOC_TYPE(8) TYPE C VALUE 'IDOC'.
DATA:
IDOC_CONTROL LIKE EDIDC,
T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
*Reads data from Z table
SELECT *
FROM ZTABLE
INTO TABLE L_ZTABLE.
*Set the control data info required for the distribution
IDOC_CONTROL-MESTYP = Z_MESTYPE.
IDOC_CONTROL-DOCTYP = Z_IDOC_TYPE.
*Populate the IDoc
LOOP AT L_ZTABLE.
CLEAR IDOC_DATA.
IDOC_DATA-SEGNAM = Z_SEGNAME.
IDOC_DATA-SDATA = ZTABLE.
APPEND IDOC_DATA.
ENDLOOP.
*Deliver the IDOC as defined in distribution model/partner profile
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
EXPORTING
MASTER_IDOC_CONTROL = IDOC_CONTROL
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_CONTROL
MASTER_IDOC_DATA = IDOC_DATA
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5.
IF sy-subrc = 0.
COMMIT WORK.
ENDIF. -
ALE/IDOC[custom table]
Hi All,
I have a doubt regarding the type of programs used to post the idocs using ALE in the outbound process.
Please also tell me which program I will use to post a custom table of mine to another server using ALE/IDOC.
Please also tell me the procedure to do the same mentioned above.
Please help. Its a urgent requirement...........................
Thanks in advance......................................................hi,
u can do it using CHANGE POINTERS method.For this u need to do the following configurations.
1>WE81
2>WE31
3>WE30
4>WE82
5>SCDO
6>BD61
7>BD52
8>BD50
9>BD60
10>WE20
11>BD64.
First create an object in tcode -SCDO,there u specify ur tablename.
now the fields which are there in the ztable,in the further characteristics of the dataelement u need to check the check box CHANGE DOCUMENT HEADER.Now in SCDO u need to generate the upgarde program,the sap will generate four includes,u need to call them in ur program.
U need to write one FM ,where u need to use the FM's.
CHANGE_POINTERS_READ,
CHANGE_POINTERS_STATUS_WRITE.
Regards,
nagaraj -
Implementation of IDOC types FINSTA01 and PEXR2002
Hi All,
I want to implement the 2 IDOC types PEXR2002 and FINSTA01 using EDI.The requirement is like I have to generate both the inbound and outbound processing for both the IDOC types using EDI.
I have the following queries :
1)What are the basic fields that are required for both the inbound and outbound processing(like file format)
2)How the inbound and outbound processing will be triggered like how can I send the file from SAP to EDI or how can I get the file from EDI to SAP and how to uplaod the record into SAP is there any SAP standard transactions or any standard reports or do I have to configure in the SPRO etc.
3)What are the settings that I have to configure?
Please help me out and your help will be appreciated.
Thanks and Regards,
Ramesh.Hello Ramesh,
The answers to your questions are a few chapters in some books, meaning its quite large.
But in short.
1. the minimum fields are what is required by that particular transaction in SAP for inbound and for outbound you gotta check with the receiving party what they need.
example , if you are posting a PO in SAP, then what are the mandatory fields, thats the minimum.
With every idoc , incoming, there are a few ways to post, most common is via function modules.
Lets say you know a partner which will communicate via EDI, you have to maintain a partner profile in WE20.
There you define the incoming and outgoing messages.
Every message has, idoc type.
Transactions WE42 and WE43 are where you define a process code for attaching the message type/idoc type to a Funtion module.
Also there is config for setting up output types, see transaction NACE.
This is a process with lots of parameters.
You would be better off getting a book which explains it all in a proper order. -
BD10 and BD21 - Idoc custom segment - Error in BD21 but no error in BD10
Hi All,
I have a custom segment 'ZXXXXX' added to MATMAS05 idoc type.
When I use BD10 to send a material to another system I don't have any errors but when I use BD21 Change pointers I'm getting an internal error.
Is there something I need to add so that it works both for BD10 and BD21 without any errors?
Please help.
MeghnaDo you have a filter in the distribution model for a field in your custom segment ?
If yes ... you have to assign parameter CIMTYP (changing parameter) in your customer exit with the Value of your "IDoc Extensionname"
Example:
IDOCTP = MATMAS05
Extzension = ZZMATMAS
P_CIMTYP = 'ZZMATMAS'.
That´s all ! -
Ale / Idoc Customer master
hi all,
i am working with ale/idoc .
from one client i am sending customer master data using DEBMAS
I have checked in IDOC
for contact person
it is not picking fax number and email
and telephone number it is picking from KNA1 table
reagrds,
mohd.Hi,
the data you try to distribute, even if related to customer master data, does not belong to it.
It belongs to the Business Address Services (BAS).
As a result, to distribute it you need to distribute ADR*MAS idocs types too.
According to the fields you try to distribute, idocs types ADR2MAS and ADR3MAS are definitively necessary.
You should look at [note 384462|https://service.sap.com/sap/support/notes/384462] and [note 306275 - Transferring address data|https://service.sap.com/sap/support/notes/306275].
Best regards
Alain -
Inbound Idoc customer number conversion
I am new to EDI and have a question to ask you both about inbound IDOC's. We have customers sending remittance advices through EDI. The customer numbers in them are their own customer numbers. In SAP, we maintain different customer numbers. Where do the mapping of the customer numbers take place -- In the EDI subsytem itself or in SAP? If in SAP, can you let me know the procedure to do this.
Any help will be appreciated and points awarded.
Thanks,
Nile.Hey Fren,
1. Data Mapping
Within the framework of SAP EDI, the conversion of a business document in IDoc format to an EDI standard format (and vice versa) is the most important task performed by a subsystem. This process is resource intensive and, hence, is better done at the subsystem level than within SAP. The following conversions and translations are carried out by the subsystem.
Creating a control record for each inbound IDoc.
An inbound IDoc must have a control record. The EDI subsystem builds the control record using the information stored in its local repository or from the SAP repository.
Removing the control record during the outbound process.
The control record in the IDoc file is used by the subsystem for housekeeping functions, such as locating the trading partner profile. The data on the control record is not needed for translating the content of the EDI documents.
Translating data from IDoc format to EDI format.
For an outbound transaction, the EDI subsystem converts data in the IDoc format to a suitable EDI format.
Translating data from EDI format to IDoc format.
For an inbound transaction, the EDI subsystem converts data in the standard EDI format to IDoc format.
Bundling and unbundling IDocs.
If several IDocs are passed to the EDI subsystem in one file, the subsystem separates them into individual documents. Similarly, on the inbound process the subsystem can bundle multiple IDocs into a single file to improve performance.
2 Maintaining the Partner Profile
A partner is defined as the business partner with whom you conduct business and exchange EDI documents. These partners are not necessarily the same as the partners in the partner profile of SAP. However, the concept is quite similar. In SAP, the partner profile maintains parameters specific to the IDoc process, and in the subsystem the partner profile maintains parameters specific to the EDI process. Some typical attributes in a partner profile are
· A unique partner number
· The partner type (Customer, Vendor)
· The standard used (EDIFACT, ANSI X12, and so on)
· The version of the EDI standard
· The EDI message exchanged (850, 860, ORDERS, ORDCHG)
· A functional acknowledgment flag
3 Triggering the Inbound Process
After receiving an inbound EDI transmission and creating an IDoc file, the subsystem is often responsible for triggering the inbound process. SAP provides a program named startrfc to start any RFC−enabled function module from the operating system level. For the EDI process, the subsystem uses the startrfc program to
trigger the function module EDI_DATA_INCOMING. Chapter 6, "Configuring Basic EDI Components," provides the complete details and parameters of the startrfc progam.
4 Reporting Process Status to SAP
In an outbound process, after an IDoc has been transferred from SAP to the subsystem, SAP loses control over the process. However, SAP maintains visibility into the process by requiring the subsystem to report on the status of the process. SAP provides a file interface for the subsystem to send a status report at every milestone.
I hope you got some idea from this process.....
<REMOVED BY MODERATOR>
Warm Regards,
Abhi...
Edited by: Alvaro Tejada Galindo on Apr 25, 2008 4:36 PM -
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 -
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. -
IDoc - Custom segments added?
Hi,
I am new to IDOC and working on Sales Order BOM inbound interface. Using BOMORD01 Idoc and filling E1STZUM, E1KDSTM and E1STPON segments. Getting a message saying "Segment cannot be identified" (ZE1FIKP) and also "Custom segments added" but actually my intention is not to add any custom segments, why I am getting this message and how to correct it.
Thanks in advance.
Regards,
Balaji Viswanath.Hi,
Just For your understanding...
There are basically two types of IDOCs.
Basic IDOCs
Extended IDOCs
Idoc Components
Basic Idoc
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extension Idoc
Extending the functionality by adding more segments to existing Basic IDOCs.
Creation of IDoc
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
create IDOC Type
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
for futher info check the below links
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sap-img.com/
http://www.sappoint.com/abap.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
<b>if u find it useful plz mark the points</b> -
Hello all.
I am receiving a IDoc for a customer, wich creates a sales order.
I need to receive diferent IDocs for one customer, but create the sales order in a diferent customer (wich is determinated by the contents of the IDoc).
Is there any way (maybe user exit) to change the customer in wich the sales order is created?
Thanks in advance
Nuno SilvaHi,
I suggest to check on inbound process codes DELV (linked with FM 'IDOC_INPUT_DELVRY').
The latest DELVRY* basic type is DELVRY07 which you can use.
Regards,
Dominik Modrzejewski
Maybe you are looking for
-
Cannot send email using Gmail after iOS 5
Since updating to iOS 5, I cannot send email from my Gmail account on my iPhone. I receive email fine, but when trying to send I get the error: Cannot Send Mail Check the settings for the outgoing servers in Settings > Mail, Contacts, Calendars I hav
-
So basically I tried to back up my itunes library to my external hard drive and when I followed the instructions and then went to play a song it said Orginal file cannot be found. It said that for all of the songs. I'm not sure how to fix what I did,
-
Hi experts , I have a requirement which is very simple to BPM experts and many similar blogs are available in SDN. The issue is mine is a file to idoc scenario, 8 files in a folder of different structure and 1 idoc in tar
-
Differece bet GLPCA and GLPCT in ECC 6 with classic PCA
Hi Ajay and Experts, Thank you for helping me till now for all the issues in COPC and COPA we are all set. I found once issue in PCA today as below, can anyone please give inputs. I have reviewed all the threads but i want to specify my case first. W
-
Who can tell me the details about "JMSJVMOPTS" environment variable of JMSC API
I have a question about JMS C API. When in windows service application, JMSContectCreate return JMS_JVM_ERROR error. But in desktop app, it does well. I think I may need set the JMSJVMOPTS environment variable.