Clarification sought on 'Qualifiers'-segment in ALE

Hi friends,
Could anyone plz explain me about the qualifiers which comes under segment in ALE.Thanks in advance.Urgent.

Ok, so the login process APEX creates when you create a new application handles the post login stuff. Now if this is an automatic feature then perhaps the Post-Authentication Process Help should be changed to reflect this. Now to work on the Logout URL

Similar Messages

FA Account Generator: Non Qualified Segment

Hi,
Currently we have a requirement of customizing the account generator to accommodate the following requirement.
COA structure: Company-Branch-CostCenter-NaturalAccount-Product-Future1
The account generator should generate the Account based on the Branch and the CostCenter that owns the asset.
I understand that we can get Cost Center segment value in FA account generator.(by using the Cost center qualifier)
Currently i need to derive the non qualifier segment BRANCH also.
Can someone throw some light on this, like how can this be acheived?
Regards,
Senthil
Edited by: Senthil Velavan J R on Oct 8, 2009 2:59 PM

Accounting Segments that are not qualifiers will have to be derived programmatically.

Populate Segments in ALE

Hai Friends....
 How to Populate the Segment in ALE...
 Please Help me....
 BalajeeKannan

Hi,
You do not have to populate IDOC data in ALE. SAP does it for you using standard function module. Let's say you are using ALE to distribute material master record, you use transaction BD10.
Also, before using ALE you need to finish certain configuration. This is done in transaction SALE.
Check this link. This describe the scenario where you use your custom IDOC in ALE.
http://www.erpgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
Check these link for more information regarding ALE.
http://help.sap.com/saphelp_46c/helpdata/en/78/2173cf51ce11d189570000e829fbbd/frameset.htm
http://help.sap.com/saphelp_46c/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
Let me know if you need any other information.
Regards,
Rs

Clarification sought about Application type and library availability

I am new to Adobe's product line and am confused about something and would be grateful for some clarification.
In Flex Builder 3 when creating a new Project, there is an Application type radio button:
O Web application (runs in Flash Player)
O Desktop application (runs in Adobe AIR)
Is my understanding correct that if I choose "Web application", classes identified in the documentation as "AIR only" (e.g. HTMLLoader class) will be unavailable to my app?
Here's the source of my confusion. The class is called flash.html.HTMLLoader and the class is found in the flash.html package, but the documentation reads "(AIR only)".
Do I have to choose "Desktop application" when creating the new project if I want the app to have access to the HTMLLoader class (and others marked "AIR" in the docs)?
Thanks

Yes, that's exactly right.
I assume the source of the confusion is that the "AIR only" classes are still in the flash.* package. In the early days there was some discussion back and forth about the appropriate place to put AIR only classes. In the end it was decided that they would be in the same top-level package as the Flash Player classes.
(To add to the confusion, there is also an air.* package. That package contains classes that are AIR-only but are not built-in to AIR. In other words, they're additional code libraries that make certain functionality easier, but they're written in ActionScript and run on top of AIR just like any ActionScript code you write, rather than being part of the AIR runtime.)

Clarification on the E1EDPA1 Segment in IDOCS

Hello Team,
I have this doubt,
For an inbound IDOC (orders05) , I just got to know that segment E1EDPA1 relates to partner information at the item level,
I am trying to loop the internal table IDOC_DATA for segment E1EDPA1 and extract the partner details (partn,parvw) for each segment.
But i'm just confused about this..
If we mean that the E1EDPA1 segment relates to the partner information at the item level, does that Imply that we will have the same number of E1EDPA1 segments as the number of line items in the IDOC?
In other words, lets say the Inbound IDOC contains 3 line items, would that mean we have 3 E1EDPA1 segments in the IDOC, where each segment correspond to a single line item?
Any help would be highly appreciated..

when you dbl-click, it will ask you to create this include and will also warn you, once it warns, you go ahead by pressing enter key.
and you end up within this include where you can write your own code.
Regards.

CRM2015: AD Domain Functional Levels Ambiguity - Clarification Sought

In the Planning and Deployment guide (page 17) It states.
The domain where the server is located must be running in one of the following Active Directory domain functional levels:
Windows Server 2008 Modes
Windows Server 2008 R2 Modes
Windows Server 2012 Modes
For more information about Active Directory domain and forest modes, see:
Understanding Active Directory Domain Services (AD DS) Functional Levels
Active Directory (Windows Server 2012 R2)
Windows 2000 Server forest and domain modes are not supported with this version of Microsoft Dynamics CRM.
When it states Windows Server 2008 Modes, does it mean only 2008 modes, or the modes supported by 2008. As I believe one of the 2008 Modes is 2003 Native and Interim.
Can anybody confirm if AD controllers must be 2008 or higher to support CRM?

Backing Up - Clarification Sought Please...

Hello,
I'm using iTunes 7.0.2 and would appreciate a clarifiation regarding backing up using the 'Back Up To Disc' facility.
I'd like to back up my whole library (I have made a separate disc of purchased music) to save having to re-rip stacks of CD's in the event of having to restore the music.
If you use the back-up facility, does it save/burn the music as smaller data files as opposed to the actual, larger MP3/Apple Lossless files?
My Mac mini hasn't got a DVD burner, so I'm having to use CD's. Data files are naturally more appealing since I can get more files on each disc. As it is purely for back-up purposes, the fact they can't be played as a conventional music CD isn't an issue.
Thanks for your help.
Mac mini 1.42Ghz, 512MB, Airport, Bluetooth, Combo Mac OS X (10.4.8)

If you use the back-up facility, does it save/burn the music as smaller data files as opposed to the actual, larger MP3/Apple Lossless files?
A data file and MP3/Apple Lossless files are the same thing.
It does not burn them as audio discs.

IDOC - segment Qualifier

Dear all,
Do you know the transaction or an document which give the link between the Qualifier segment of an segment IDOC and the SAP field ?
for example : IDOC ORDERS05
segment E1EDK03
qualifier 002 : wished delivery date in VA01
segment E1EDK02
qualifier 050 : Delivery Order in segment description but correspond to PO number in VA01
I search to fill in the field PO Date but I don't find the qualifer segment.
Could you please help me ?
thanks
Véronique

Hi friends,
i thing your problem will solve.
E1EDK01 : IDoc: Document header general data
Segment definition E2EDK01005 Released since Release 45B , Segment length: 0357
ACTION : Action code for the whole EDI message
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
KZABS : Flag: order acknowledgment required
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 002, Offset : 0066. external length : 000001
CURCY : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 003, Offset : 0067. external length : 000003
HWAER : EDI local currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 004, Offset : 0070. external length : 000003
WKURS : Exchange rate
internal data type : CHAR
Internal length : 000012 characters
Position in segment : 005, Offset : 0073. external length : 000012
ZTERM : Terms of payment key
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 006, Offset : 0085. external length : 000017
KUNDEUINR : VAT Registration Number
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 007, Offset : 0102. external length : 000020
EIGENUINR : VAT Registration Number
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 008, Offset : 0122. external length : 000020
BSART : Document type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 009, Offset : 0142. external length : 000004
BELNR : IDOC document number
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 010, Offset : 0146. external length : 000035
NTGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 011, Offset : 0181. external length : 000018
BRGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 012, Offset : 0199. external length : 000018
GEWEI : Weight unit
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 013, Offset : 0217. external length : 000003
FKART_RL : Invoice list type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 014, Offset : 0220. external length : 000004
ABLAD : Unloading Point
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 015, Offset : 0224. external length : 000025
BSTZD : Purchase order number supplement
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 016, Offset : 0249. external length : 000004
VSART : Shipping Conditions
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 017, Offset : 0253. external length : 000002
VSART_BEZ : Description of the Shipping Type
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 018, Offset : 0255. external length : 000020
RECIPNT_NO : Number of recipient (for control via the ALE model)
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 019, Offset : 0275. external length : 000010
KZAZU : Order Combination Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 020, Offset : 0285. external length : 000001
AUTLF : Complete delivery defined for each sales order?
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 021, Offset : 0286. external length : 000001
AUGRU : Order reason (reason for the business transaction)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 022, Offset : 0287. external length : 000003
AUGRU_BEZ : Description
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 023, Offset : 0290. external length : 000040
ABRVW : Usage Indicator
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 024, Offset : 0330. external length : 000003
ABRVW_BEZ : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 025, Offset : 0333. external length : 000020
FKTYP : Billing category
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 026, Offset : 0353. external length : 000001
LIFSK : Delivery block (document header)
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 027, Offset : 0354. external length : 000002
LIFSK_BEZ : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 028, Offset : 0356. external length : 000020
EMPST : Receiving point
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 029, Offset : 0376. external length : 000025
ABTNR : Department number
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 030, Offset : 0401. external length : 000004
DELCO : Agreed delivery time
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 031, Offset : 0405. external length : 000003
WKURS_M : Indirectly quoted exchange rate in an IDoc segment
internal data type : CHAR
Internal length : 000012 characters
Position in segment : 032, Offset : 0408. external length : 000012
E1EDK14 : IDoc: Document Header Organizational Data
Segment definition E2EDK14 Released since Release 30A , Segment length: 0038
QUALF : IDOC qualifer organization
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
ORGID : IDOC organization
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
E1EDK03 : IDoc: Document header date segment
Segment definition E2EDK03 Released since Release 30A , Segment length: 0017
IDDAT : Qualifier for IDOC date segment
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
DATUM : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 002, Offset : 0066. external length : 000008
UZEIT : IDOC: Time
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 003, Offset : 0074. external length : 000006
E1EDK04 : IDoc: Document header taxes
Segment definition E2EDK04001 Released since Release 40B , Segment length: 0107
MWSKZ : VAT indicator
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 001, Offset : 0063. external length : 000007
MSATZ : VAT rate
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 002, Offset : 0070. external length : 000017
MWSBT : Value added tax amount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 003, Offset : 0087. external length : 000018
TXJCD : Tax Jurisdiction
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 004, Offset : 0105. external length : 000015
KTEXT : Text Field
internal data type : CHAR
Internal length : 000050 characters
Position in segment : 005, Offset : 0120. external length : 000050
E1EDK05 : IDoc: Document header conditions
Segment definition E2EDK05001 Released since Release 40A , Segment length: 0185
ALCKZ : Surcharge or discount indicator
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
KSCHL : Condition type (coded)
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 002, Offset : 0066. external length : 000004
KOTXT : Condition text
internal data type : CHAR
Internal length : 000080 characters
Position in segment : 003, Offset : 0070. external length : 000080
BETRG : Fixed surcharge/discount on total gross
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 004, Offset : 0150. external length : 000018
KPERC : Condition percentage rate
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 005, Offset : 0168. external length : 000008
KRATE : Condition record per unit
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 006, Offset : 0176. external length : 000015
UPRBS : Price unit
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 007, Offset : 0191. external length : 000009
MEAUN : Unit of measurement
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 008, Offset : 0200. external length : 000003
KOBTR : IDoc condition end amount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 009, Offset : 0203. external length : 000018
MWSKZ : VAT indicator
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 010, Offset : 0221. external length : 000007
MSATZ : VAT rate
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 011, Offset : 0228. external length : 000017
KOEIN : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 012, Offset : 0245. external length : 000003
E1EDKA1 : IDoc: Document Header Partner Information
Segment definition E2EDKA1003 Released since Release 45A , Segment length: 0995
PARVW : Partner function (e.g. sold-to party, ship-to party, ...)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
PARTN : Partner number
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 002, Offset : 0066. external length : 000017
LIFNR : Vendor number at customer location
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 003, Offset : 0083. external length : 000017
NAME1 : Name 1
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 004, Offset : 0100. external length : 000035
NAME2 : Name 2
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 005, Offset : 0135. external length : 000035
NAME3 : Name 3
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 006, Offset : 0170. external length : 000035
NAME4 : Name 4
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 007, Offset : 0205. external length : 000035
STRAS : Street and house number 1
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 008, Offset : 0240. external length : 000035
STRS2 : Street and house number 2
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 009, Offset : 0275. external length : 000035
PFACH : PO Box
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 010, Offset : 0310. external length : 000035
ORT01 : City
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 011, Offset : 0345. external length : 000035
COUNC : County code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 012, Offset : 0380. external length : 000009
PSTLZ : Postal code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 013, Offset : 0389. external length : 000009
PSTL2 : P.O. Box postal code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 014, Offset : 0398. external length : 000009
LAND1 : Country Key
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 015, Offset : 0407. external length : 000003
ABLAD : Unloading Point
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 016, Offset : 0410. external length : 000035
PERNR : Contact person's personnel number
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 017, Offset : 0445. external length : 000030
PARNR : Contact person's number (not personnel number)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 018, Offset : 0475. external length : 000030
TELF1 : 1st telephone number of contact person
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 019, Offset : 0505. external length : 000025
TELF2 : 2nd telephone number of contact person
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 020, Offset : 0530. external length : 000025
TELBX : Telebox number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 021, Offset : 0555. external length : 000025
TELFX : Fax number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 022, Offset : 0580. external length : 000025
TELTX : Teletex number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 023, Offset : 0605. external length : 000025
TELX1 : Telex number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 024, Offset : 0630. external length : 000025
SPRAS : Language key
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 025, Offset : 0655. external length : 000001
ANRED : Form of Address
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 026, Offset : 0656. external length : 000015
ORT02 : District
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 027, Offset : 0671. external length : 000035
HAUSN : House number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 028, Offset : 0706. external length : 000006
STOCK : Floor
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 029, Offset : 0712. external length : 000006
REGIO : Region
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 030, Offset : 0718. external length : 000003
PARGE : Partner's gender
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 031, Offset : 0721. external length : 000001
ISOAL : Country ISO code
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 032, Offset : 0722. external length : 000002
ISONU : Country ISO code
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 033, Offset : 0724. external length : 000002
FCODE : Company key (France)
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 034, Offset : 0726. external length : 000020
IHREZ : Your reference (Partner)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 035, Offset : 0746. external length : 000030
BNAME : IDoc user name
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 036, Offset : 0776. external length : 000035
PAORG : IDOC organization code
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 037, Offset : 0811. external length : 000030
ORGTX : IDoc organization code text
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 038, Offset : 0841. external length : 000035
PAGRU : IDoc group code
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 039, Offset : 0876. external length : 000030
KNREF : Customer description of partner (plant, storage location)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 040, Offset : 0906. external length : 000030
ILNNR : Character field, length 70
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 041, Offset : 0936. external length : 000070
PFORT : PO Box city
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 042, Offset : 1006. external length : 000035
SPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 043, Offset : 1041. external length : 000002
TITLE : Title
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 044, Offset : 1043. external length : 000015
E1EDKA3 : IDoc: Document Header Partner Information Additional Data
Segment definition E2EDKA3 Released since Release 30D , Segment length: 0073
QUALP : IDOC Partner identification (e.g.Dun&Bradstreet number)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
STDPN : Character field, length 70
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 002, Offset : 0066. external length : 000070
E1EDK02 : IDoc: Document header reference data
Segment definition E2EDK02 Released since Release 30A , Segment length: 0058
QUALF : IDOC qualifier reference document
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
BELNR : IDOC document number
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
POSNR : Item number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 003, Offset : 0101. external length : 000006
DATUM : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 004, Offset : 0107. external length : 000008
UZEIT : IDOC: Time
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 005, Offset : 0115. external length : 000006
E1EDK17 : IDoc: Document Header Terms of Delivery
Segment definition E2EDK17 Released since Release 30A , Segment length: 0076
QUALF : IDOC qualifier: Terms of delivery
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
LKOND : IDOC delivery condition code
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0066. external length : 000003
LKTEXT : IDOC delivery condition text
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 003, Offset : 0069. external length : 000070
E1EDK18 : IDoc: Document Header Terms of Payment
Segment definition E2EDK18 Released since Release 30A , Segment length: 0089
QUALF : IDOC qualifier: Terms of payment
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
TAGE : IDOC Number of days
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 002, Offset : 0066. external length : 000008
PRZNT : IDOC percentage for terms of payment
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 003, Offset : 0074. external length : 000008
ZTERM_TXT : Text line
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 004, Offset : 0082. external length : 000070
E1EDK35 : IDoc: Document Header Additional Data
Segment definition E2EDK35000 Released since Release 45A , Segment length: 0078
QUALZ : Qualifier for IDoc additional data
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
CUSADD : Data Element Type CHAR Length 35
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
CUSADD_BEZ : Character field of length 40
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 003, Offset : 0101. external length : 000040
E1EDK36 : IDOC: Doc.header payment cards
Segment definition E2EDK36000 Released since Release 45A , Segment length: 0114
CCINS : Payment cards: Card type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 001, Offset : 0063. external length : 000004
CCINS_BEZEI : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 002, Offset : 0067. external length : 000020
CCNUM : Payment cards: Card number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 003, Offset : 0087. external length : 000025
EXDATBI : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 004, Offset : 0112. external length : 000008
CCNAME : Payment cards: Name of cardholder
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 005, Offset : 0120. external length : 000040
FAKWR : Maximum amount
internal data type : CURR
Internal length : 000015 characters
000002 decimal places, without sign
Position in segment : 006, Offset : 0160. external length : 000017
E1EDKT1 : IDoc: Document Header Text Identification
Segment definition E2EDKT1002 Released since Release 45A , Segment length: 0089
TDID : Text ID
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 001, Offset : 0063. external length : 000004
TSSPRAS : Language Key
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0067. external length : 000003
TSSPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 003, Offset : 0070. external length : 000002
TDOBJECT : Texts: Application Object
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 004, Offset : 0072. external length : 000010
TDOBNAME : Name
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 005, Offset : 0082. external length : 000070
E1EDKT2 : IDoc: Document Header Texts
Segment definition E2EDKT2001 Released since Release 40A , Segment length: 0072
TDLINE : Text line
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 001, Offset : 0063. external length : 000070
TDFORMAT : Tag column
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 002, Offset : 0133. external length : 000002
E1EDP01 : IDoc: Document Item General Data
Segment definition E2EDP01007 Released since Release 640 , Segment length: 0542
POSEX : Item number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 001, Offset : 0063. external length : 000006
ACTION : Action code for the item
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0069. external length : 000003
PSTYP : Item Category
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 003, Offset : 0072. external length : 000001
KZABS : Flag: order acknowledgment required
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 004, Offset : 0073. external length : 000001
MENGE : Quantity
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 005, Offset : 0074. external length : 000015
MENEE : Unit of measure
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 006, Offset : 0089. external length : 000003
BMNG2 : Quantity in price unit
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 007, Offset : 0092. external length : 000015
PMENE : Price Unit of Measure
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 008, Offset : 0107. external length : 000003
ABFTZ : Agreed cumulative quantity
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 009, Offset : 0110. external length : 000007
VPREI : Price (net)
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 010, Offset : 0117. external length : 000015
PEINH : Price unit
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 011, Offset : 0132. external length : 000009
NETWR : Item value (net)
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 012, Offset : 0141. external length : 000018
ANETW : Absolute net value of item
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 013, Offset : 0159. external length : 000018
SKFBP : Amount qualifying for cash discount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 014, Offset : 0177. external length : 000018
NTGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 015, Offset : 0195. external length : 000018
GEWEI : Weight unit
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 016, Offset : 0213. external length : 000003
EINKZ : Flag: More than one schedule line for the item
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 017, Offset : 0216. external length : 000001
CURCY : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 018, Offset : 0217. external length : 000003
PREIS : Gross price
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 019, Offset : 0220. external length : 000018
MATKL : IDOC material class
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 020, Offset : 0238. external length : 000009
UEPOS : Higher-Level Item in BOM Structures
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 021, Offset : 0247. external length : 000006
GRKOR : Delivery group (items delivered together)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 022, Offset : 0253. external length : 000003
EVERS : Shipping instructions
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 023, Offset : 0256. external length : 000007
BPUMN : Denominator for Conv. of Order Price Unit into Order Unit
internal data type : DEC
Internal length : 000005 characters
No decimal places, without sign
Position in segment : 024, Offset : 0263. external length : 000006
BPUMZ : Numerator for Conversion of Order Price Unit into Order Unit
internal data type : DEC
Internal length : 000005 characters
No decimal places, without sign
Position in segment : 025, Offset : 0269. external length : 000006
ABGRU : Reason for rejection of quotations and sales orders
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 026, Offset : 0275. external length : 000002
ABGRT : Description
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 027, Offset : 0277. external length : 000040
ANTLF : Maximum number of partial deliveries allowed per item
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 028, Offset : 0317. external length : 000001
FIXMG : Delivery date and quantity fixed
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 029, Offset : 0318. external length : 000001
KZAZU : Order Combination Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 030, Offset : 0319. external length : 000001
BRGEW : Total weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 031, Offset : 0320. external length : 000018

Flexfield & Segment Qualifier

Hi
I have read about the Flexfield Qualifier & Segment Qualifier for Flexfield but I cannot clear concept for the same.
Can anyone explain the same with example, if possible .
Thanks to all of you in advance.
sanjay

Hi sanjay;
Please check:
Oracle Applications Flexfields Guide
http://download.oracle.com/docs/cd/A60725_05/pdf/flex.pdf
Also check
tell me the use of Segment Qualifier and flexfield qualifier
http://www.geekinterview.com/question_details/14754
Hope it helps
Regard
Helios

Segment Qualifier & Element Qualifier

Hi,
    what is Segment Qualifier & Element Qualifier in EDI?
what is the difference between these two.
Thanks,
Rajeswari

Hi rajeshwari,
here are the simple definition of segment and element qualifier
Segment:-
EDI documents are comprised of a series of records called segments. Every segment begins with a segment identifier, also called a segment code. The segments are delimited. A special character or characters designate where one segment ends and another begins. Usually segment delimiters include a line return, so we usually think of a segment as a line of an EDI document.
Element:-
A segment is comprised of a series of elements. These elements are delimited by a special character called a element seperator.
Difference
The segment code specifies what the elements in the segment represent. For instance, the first element of an DTM segment is date/time qualifier and the second element is the date. The first element of a REF segment is the reference identification qualifier and the second element is the reference identifier. We refer to elements by their sequence within the segment. For example, we refer to the first element within a REF segment as element REF01, the second as REF02, and so forth.
Example
The following X12 EDI document fragment contains eight (8) segments.
     ST850397822~
     BEG00RE1234*980208~
     REFAHM109~
     REFDP641~
     REFIA000100685~
     DTM010970918~
     N1BY92*1287~
     N1ST92*87447~
for more details you can follow this link
http://www.usonia.net/ricker/?page_id=20
hope this may help you
Thanks
sandeep
PS:reward points if helpful

What is meaning of Qualifier

What is meaning of Qualifier

Hello Asha
I assume you came across this term while dealing with ALE/IDoc/EDI.
If you look at message type INVOIC02 it contains the following segments:
SEGMENTTYP     SEGMENTDEF     QUALIFIER     DESCRP
Segment type in 30-character format     IDoc Development : Segment definition     Flag: Qualified segment in IDoc     Short description of object
E1EDK01                            E2EDK01005                               IDoc: Document header general data
E1EDKA1                            E2EDKA1003                         X     IDoc: Document Header Partner Information
E1EDK02                            E2EDK02                            X     IDoc: Document header reference data
E1EDK03                            E2EDK03                            X     IDoc: Document header date segment
E1EDK05                            E2EDK05001                         X     IDoc: Document header conditions
E1EDK04                            E2EDK04001                         X     IDoc: Document header taxes
E1EDK17                            E2EDK17                            X     IDoc: Document Header Terms of Delivery
E1EDK18                            E2EDK18                            X     IDoc: Document Header Terms of Payment
E1EDK23                            E2EDK23001                         X     IDoc: Document Header Currency Segment
E1EDK28                            E2EDK28                                  IDoc: Document Header Bank Data
E1EDK29                            E2EDK29003                               IDoc: Document Header General Foreign Trade Data
E1EDKT1                            E2EDKT1002                         X     IDoc: Document Header Text Identification
E1EDKT2                            E2EDKT2001                               IDoc: Document Header Texts
E1EDK14                            E2EDK14                            X     IDoc: Document Header Organizational Data
E1EDP01                            E2EDP01007                               IDoc: Document Item General Data
E1EDP02                            E2EDP02001                         X     IDoc: Document Item Reference Data
E1EDP03                            E2EDP03                            X     IDoc: Document Item Date Segment
E1EDP19                            E2EDP19001                         X     IDoc: Document Item Object Identification
E1EDP26                            E2EDP26                            X     IDoc: Document Item Amount Segment
E1EDPA1                            E2EDPA1003                         X     IDoc: Doc.item partner information
E1EDP05                            E2EDP05002                         X     IDoc: Document Item Conditions
E1EDP04                            E2EDP04001                         X     IDoc: Document Item Taxes
E1EDP28                            E2EDP28003                               IDoc: Document Item - General Foreign Trade Data
E1EDP08                            E2EDP08                                  IDoc: Package data individual
E1EDP30                            E2EDP30000                         X     IDOC: Document Item Account Assignment Intercompany Billing
E1EDPT1                            E2EDPT1001                         X     IDoc: Document Item Text Identification
E1EDPT2                            E2EDPT2001                               IDoc: Document Item Texts
E1EDS01                            E2EDS01                            X     IDoc: Summary segment general
The flag QUALIFIER = 'X' means the same segment is used to hold different data depending on the qualifier.
For example, segment E1EDK03 contains the following qualifiers in field IDDAT:
FLDVALUE_L     DESCRP
001     Delivery date (supplier)
002     Requested delivery date (customer)
003     Closing date for applications
004     Deadline for submission of quotations
005     Quotation/inquiry valid from
006     Binding period for a quotation (valid to)
007     Reconciliation date for agreed cumulative quantity
008     First firm zone
009     Second firm zone
010     Shipping date
011     Date IDOC created
012     Document date
013     Quotation date (supplier)
014     Inquiry date (customer)
015     Invoice posting date (Invoice tax point date)
016     Invoice date
017     Payment Date
018     Bill of exchange date
019     Start of validity for outline agreement or inquiry
020     End of validity for outline agreement orinquiry
021     Billing date for invoice list
022     Purchase order date
023     Pricing date
024     Fixed value date
025     Created on
026     Billing date for billing index and printout
027     Date on which services rendered
028     Due date
029     Sales order date
030     Goods receipt date
031     Planned date
032     Date of reference number
033     Shipment start date
034     Planned shipment end date
035     Goods issue date
036     Bank value date
037     Bank offsetting date
038     Posting to bank
039     Ship-to party's PO date
040     Pickup date from (delivery order)
041     Pickup date to (delivery order)
042     Date of old balance
043     Date of new balance
044     Payment baseline date
045     Shelf life expiration data for batch
046     Date for Delivery Relevance
101     Resale Invoice Date
102     Resale Ship Date
103     Booking from date
104     Booking to date
105     Shipping from date
106     Shipping to date
107     Billing from date
108     Billing to date
109     Exercise from date
110     Exercise to date
The qualifiers are required if you need to map IDoc format to an EDI format (e.g. EDIFACT, TRADACOM, ANSI.X12, etc.) and vice versa.
Regards
Uwe

Segment Name with extra information in WE02.

Hello SAPients!
I created an IDoc Extension for basic type WBBDLD04 and modified the corresponding BAdI. Everything works fine, the extra segment is correctly added and the information in the Segment is correct. The only problem I have is that in TCode WE02/WE05 the name of the segment appears with information of the first field.
Example: The segment is ZE1WBB1 but in the tree of the Tcode WE02 appears like ZE1WBB1 1024.00 or sometimes like ZE1WBB1 0.00. That extra information corresponds to the first field of the custom segment that I created (LABST in this case)
If I look in the table EDID4 everything looks perfect. The segment name is what it should be and the SDATA field has the correct information.
What am I doing wrong?
Thanks!

I found the problem, in WE31 I just had to remove the "Qualified Segment" Checkbox and Voila!

ALE triggering ABAP program instead of iDoc

Is it possible to have ALE trigger an ABAP program instead of an iDoc?
We need to send changes in Master Data to a system that can't handle iDoc, but does know what to do with SOAP.

We're talking about an All-in-One system on NetWeaver 700 and ECC 6.0. My company has developed an Add-On for Business One and now they want to develop a similar Add-On for All-in-One. That Add-On should integrate an Open Source system into an SAP system, or at least make the flow of data seem seamless.
I should be very careful with my comments, as I'm not really understanding enough about your requirements. I must admit key words changes in master data and ALE triggered my initial comment.
On second thought it might actually be worthwhile to think about other alternatives. E.g. you could look at the technique SAP uses for BW extractors, which might also be suitable.
I might just be able to hook into the Change Doc system by defining new Change Doc and Change Pointer Types.
Well, per my comment above, maybe you don't even need change pointers. However, if you do, you can mostly rely on existing change documents unless you're dealing with some odd or custom object.
Am I right if I think that IDocs handle those Change Pointers from some kind of scheduled background job?
Part of the setup for change pointers for a specific message type is to define which function module is used for evaluating the change pointers. All change pointers are then evaluated via transaction BD21, program RBDMIDOC, which can also be scheduled in the background.
but we only need less than 5% of the information contained in an iDoc
Well, in theory SAP offers some options: You can filter segments via ALE, use reduced message types or define IDoc views. However, depending on the technique this sometimes requires that the actual application (function module creating the IDocs) has to support it (because it's additional API calls that have to be present).
Defining new IDoc types isn't that attractive to us.
Though I do understand such statement in specific cases, it's hard to relate to it on a general level. I.e. in the latter case it's often more driven by strange company policies than by good design choices.
Anyhow, in the end I'm tempted to think that change pointers with IDocs are one option among many. In your specific case however it sounds as if there's possibly other techniques that might be more suitable. So I'll stop for now before I tell you too much crap pushing you in a wrong direction...

What is the mean IDDAT field of ORDRSP idoc's E1EDP01/E1EDP03 segment

Hi experts,
I'm trying to use ORDRSP idoc to map to a target structure.
I need to know mean of IDDAT field of ORDRSP idoc's E1EDP01/E1EDP03 segment.
For example if IDDAT = 024 what does it mean?
Is there a list shows means of fields with different values?
Thanks.

Hi,
the segment E1EDP03 is a "qualified" segment.
The possible values of a qualifier field are defined in DDIC as domain value range (fixed values or by value table) of the corresponding data element.
In your case, the qualifier (data element) IDDAT has the domain DATID assigned with the T54C5 value table.
So the possible values are contained in the value table T54C5.
Using the maintenance transaction SM30 itu2019s possible change the value list; for this reason check in your system the meaning of the qualifier IDDAT = u2018024u2019.
Regards,
Andrea

BOM explosion from Production Order

Hi All,
I understand from SAP Help files that we can explode BOM from Production Order using Read PP Master Data. But it also says, that we cannot do this if items have already been issued out. So would like to know is there anyway out to ensure that the production order is reading the latest version of BOM.
The reason i want to know is because, at present the BOM keeps getting updated & so the work order has to reflect the new items. The BOM contains about 300 or more items, so manual changes is very tedious & error prone at the moment. Furthermore some components are outsourced. So i want to receive them back & post new materials for them. Hope my problem is clear & await inputs
Vivek

Hi All,
Thanks for the inputs. I think for the situation am facing, the Order change management method, should be of help, as the BOM changes does not take place on scheduled dates, for me to fix the BOM explosion dates & assign them. As of now the BOM gets changed, depending the customer requirements, which is unpredictable.
Clarification required:
1. The profile which is created using OPL7 & assigned in OPL9 is unique, i.e. for any change numbers of BOM will always follow the profile entered in 'Overall Profile' in Work Scheduling view & i do not need to create new profiles for each new change number of BOM
2. Once i run the COCM with the new change number, in the production order - components view will i be able to see any error message for those items which no longer feature in the new version of BOM? & will the materials added in the new BOM automatically feature in that list or do i have to manually add these to the order & if so, how will i know which materials need to be added?
Hope the clarifications sought are clear, await inputs
Vivek

Clarification sought on 'Qualifiers'-segment in ALE

Similar Messages

Maybe you are looking for