PR number in va01

hi all,
i want to assign different pr number range depends on plant entered in sales order. Is it possible while creating a sales order in va01.
Thanks

Hi Madhu,
Pls consult your SD cons. for SPRO setting in which no. ranges of sales order can be set as per required
Regards,
Mehfuze

Similar Messages

  • Error in va01 transaction

    Hi
      When i try to save the sales order it is throwing an error ENTER ECC NUMBER in VA01 Transaction. How to clear that error
    regards,
    PradeepM.

    Dear
    I think you have CIN implemented  in your business process .So it is asking ECC number through J1D.Otherwsise , with out CIN , you have Customer Engineering Change Status NO in item over view  : Customer number for the production series from which they release and receive materials. The customer sends this number in with a material number to request an engineering change to take effect as of a certain delivery date or cumulative quantity.
    Regards
    JH

  • Exits in VA01

    Hi all,
    Is there any exit by which i can populate the manufacturere part number into the line item customer part number in VA01.
    please let me know if any one have worked on this

    HI
    following are the exits for va01. You would have to check the appropriate one from the following
    Transaction Code - VA01                     Create Sales Order
    Exit Name           Description
    SDAPO001            Activating Sourcing Subitem Quantity Propagation
    SDTRM001            Reschedule schedule lines without a new ATP check
    V45A0001            Determine alternative materials for product selection
    V45A0002            Predefine sold-to party in sales document
    V45A0003            Collector for customer function modulpool MV45A
    V45A0004            Copy packing proposal
    V45E0001            Update the purchase order from the sales order
    V45E0002            Data transfer in procurement elements (PRreq., assembly)
    V45L0001            SD component supplier processing (customer enhancements)
    V45P0001            SD customer function for cross-company code sales
    V45S0001            Update sales document from configuration
    V45S0003            MRP-relevance for incomplete configuration
    V45S0004            Effectivity type in sales order
    V45W0001            SD Service Management: Forward Contract Data to Item
    V46H0001            SD Customer functions for resource-related billing
    V60F0001            SD Billing plan (customer enhancement) diff. to billing plan
    regards
    dinesh

  • Upon saving, assign sales order to different number range...

    Hello Experts,
    We have a new requirement wherein upon saving the sales order, I have to check its company code and
    sales document type and if it has a record in a customized table, then I have to use another number range instead
    of its default number range...
    For example, the default number range for sales orders for company code 1000 with a document type of ZAOR
    has a default number range of 3011000000 to 3011999999. I need to change it to 3021000000 to 3021999999.
    Hope you can help me guys. Thank you and take care!

    A new numner range can be created via SNRO.
    Also, you can use the following exit to assign this new numbe rrange to the order -> USEREXIT_NUMBER_RANGE
    For more info; refer Re: User Exit No for assign a different internal document number to VA01
    Neeraj

  • Number Ranges for sales document type

    Dear All,
    I have four company codes. I am assigning the same sales order type for all company codes.
    I want to have diffrent number ranges for diffrent company codes for same sales order type. Is this possible?
    Please advise
    Regards,
    Deepu Pillai

    Dear Deepu,
    A similar kind of requirement, has been stated in to the following thread:
    [Different S.O. No. Range|Re: User Exit No for assign a different internal document number to VA01;
    Include Program: MV45AFZZ
    User-Exit: USEREXIT_NUMBER_RANGE
    In the above thread, the routine has been modified as per the requirement "Different S.O. No. as per Sales Org."
    You may Discuss the same with ABAPer to modify Routine in FORM USEREXITNUMBER_RANGE_; as per the requirement: "Different S.O. No. as per Company Code"
    The user exit is called up in the FORM routine BELEG_SICHERN.
    You need define the number range depending on the selling company (VKBUR)
    Tabl
    Best Regards,
    Amit
    Note: For further assistance, if Reqd.:
    [SD Doc. No. Range Enhancement|http://www.saptechsolutions.com/pdf/SDDocumentNumberRangeEnhancements.pdf]

  • How to configure item proposal

    Hello Gurus, i'm trying to configure item proposal...but can't see the effect on VA01..i've created VA51 record for item proposal and then assigned in XD02 at sales in sales data....is there any thing else i've to still do...so that when i put the partnet function-SP number in VA01...it should give the message or record of the existing item proposal? Please correct me if i'm wrong. Thanx

    Hi,
    Item propsal is a list of materials which you can call up during the order entry.
    You create the item proposal by trazaction VA51.
    Where as Dunamic Product Prossal( which you are refering as Product proposal )is dynamic order entry tool.
    Dynamic Product proposal can be determined by different data sources as below.
    Order history.
    Listed materials .
    Excluded materials .
    Item proposal .
    Customer/material info records .
    Customer-specific data sources.
    In the dynamic product proposal You can combine/exclude materials from different data sources mentioned above.
    Say for example, you could combine the total of all materials in the last n-sales plus all materials in certain item proposals, but excluding those specified in the exclusion.
    Dynamic Product Proposal is called /determined as soon as you enter the sold party in the order.
    You can reach IMG customising steps by
    IMG >SD>Basic functions>Dynamic Product Proposal .
    regards,
    Siddharth.

  • 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

  • How to get sales order number when it is created in VA01

    hai experts,
    i have a requirement , when i create a sales order using transaction VA01 and save the transaction number , after saving i want to catch the sales order number and use in some other fucntion moudle, how can i do that  , should i use the events or any other methods to do the same
    regards
    m.a

    You can call you Z function module either from the workflow or from a BADI' where you can access the newly created sales order the BADi name is BADI_SD_V46H0001 and the method that you need to check is
    EXIT_SAPLV46H_003     Customer Function when Creating/Changing Header
    You can even call the FM from workflow too, but aganin for tht you need to create a ZBOR, if at all you are using a standard Business object and you hvae to create a new task and include that new task in the workflow by creating a new background Activity step. which I personally feel that you eed to put some more effort to fix the issue.
    Instead it is simple and sweet to call that function module from the Method which mentioned. where you can acess the sales document number tooo check int he method parameters.

  • How to get the contract number selected on VA01.

    Hello Experts,
    While creating a sales order a contract number is selected.
    ie to which contract this SO is being created.
    We get a ALV list with list of contract number and we select one.
    But no where this contract number is displayed.
    I have a placed a input/output box on additional tab header leve of VA01.
    I need to display the contract number selected by the user for that sales order on to that box.
    and this should  happened the moment the user copies the contract number from the ALV list
    any functon exit or badi's which could be used to get the value.               
    right now iam using the include MV45AFZZ
    I know the table getting used.
    Thanks in advance.
    Regards,
    Ranjith

    You can put your code into the MOVE_FIELD_TO_VBAP userexit in include MV45AFZZ. The contract information is stored on item level (VBAP) in fields WKTNR (contract number) and WKTPS (contract item). If you can have more than one contract in a sales order you should display that information on item level rather than header level, if you always reference one contract only per sales order header should be fine.
    Hope that helps,
    Michael

  • Number of Container in VA01

    Dear Gurus,
    Is there a spesific field to put number of containers in VA01?
    Kind Regards,

    Hi
    There are so many fields in salesorder.
    Any way you can use the additional data tabs at header or item level.
    regards
    Prashanth

  • Relationship b/w the PO number field in the SO creation screen(va01) and th

    Hi All,
    What is the relationship b/w the PO number field in the SO creation screen(va01) and the sales order .
    Can we maintain a specific number range for the PO Number??
    If yes where do we maintain the setting?
    Cheerzz..
    Subbz..

    Hello,
    This is nothing to do with a SAP purchase order, and you can't maintain any number range for the same as it is not a system proposed one.
    Imagine, the customer is sending a purchase order to you, and you are creating a sales order. We can give a reference to the customers PO number in this filed. It doesn't have any effect.
    It is widely used in reporting.
    Prase

  • Exit for PO number checking in VA01 Transaction.

    Hi Experts,
    Does there exists any exit to perform PO Number checking while it is been entered in the VA01 transaction.
    There is a requirement to perform some extra validation when this checking is performed.

    Hi,
    Please check the exit V45A0001.
    regards,
    Renjith Michael.

  • User-Exit after saving VA01 to get the number of Sales Order.

    Hi everyone,
    I hope you all fine!
    I really need your help to get a user-exit or BADI for the VA01 transaction,  because after pushing the save button I need to get the number of sales order, so I can create a header text, but to use a Function Module to do that, I need the sales order first.
    I hope You can help me with this.
    Thanks for your time.
    Regards,

    Hi,
          Goto se38 ,
        1. Enter prog. name  "MV45AFZZ"
        2. Choose "Enhance"  from application tool bar,
        3. Edit>Enhanc.Operations>Show implicit Enhance...
        4.Right click>Enhancement Impliment> Create....,Before that,you have to choose which subroutine is suitable for your scenario...then you can code it .
       Also,try this user exit -->"V45E0001"
    I hope ,it will help you...
    <<=< Sharing Knowlede is a way to Innovative >>=>
    By,
      Yoga

  • How to get sales order number before saving in VA01 by using parameter

    Hi,
    Please let me know how to get sales order number in transaction VA01 before saving it by using parameter in SU3.
    I tried to set parameter in SU3 "AUN", but it is not working as required, means sales order number is not appearing before saving.
    can you please suggest how to do it?
    Thanks & Regards.
    Rahul Verulkar

    Hi,
    In case of Support project, we get the high severity issues from users and needs to be closed withn 2 hours... so what we do we get the requirement from user and checking the same in production from our id, but we can not save the sales order as we are not authorized to do the same, so in such cases it is required to get the sales order number before saving... where we can guide the users.... but actuallly it is not getting saved in the table until and unless u save it manually. It works like a material master... when u create material master, the material number appears in advance in material number field "MATNR"
    If it is possible can you please suggest step by step to work on parameter in SU3 for sales order number before saving.
    Thanks & regards,
    Rahul Verulkar

  • VA01 BDC does not return sales order number

    Hi All,
    I am using BDC to create sales orders using transaction VA01. Most of the time I have no problems using this method. However, for some orders no order number is returned.
    I know that BDC is not the best way of doing things, but we have customized the sales order screens a lot and therefore can't use BAPI, so we need to use BDC.
    I have used display mode 'A' when calling the transaction and I know that all the screens populate correctly. Then when the order saves, no order number is provided. The just created order can't be found by searching using the sold-to party, so the order appears to not have created. However, when I look in the table of messages returned from the transaction, there are no errors.
    <b><REMOVED BY MODERATOR></b>
    Thanks in advance,
    Dan
    Message was edited by:
            Alvaro Tejada Galindo

    Why don't use update mode called 'S'.
    call transaction 'VA01' using BDCDATA
                           MODE 'N'
                           update 'S' -> use this one.
                           messages into bdcmsgcoll.
    Thanks
    Seshu

Maybe you are looking for

  • Acrobat 9 and X folders stay in registry and program files.

    Hi, I could see two folders of Acrobat 9 and 10 are present in my program files folder and also in registry. Our installer searches path and copy .api file in the folder. Now, it would be bit confusing for the installer to pick up the active installe

  • Totakky confused!

    Just got my 30g ipod as a gift. First I downloaded the software with the supplied disk. I have a Dell XPS computer with lots of space. When connected to my pc The "do not disconnect" screen stays on. I have downloaded songs onto my pc using limewire.

  • Can You Listen FOR while AS does something else too?

    Play and control the playing of a QT movie while also listening with Speech recognitionServer to some word from the user. i heard AS cant multithread.......

  • V480 End of Support

    When will Sun Fire V480 end of support ? Thanks a lot !

  • Some questions about SF-300 switch

    Hi Does anybody can tell me why the CLI (via SSH) in SF-300 switch works slower than in old 2950 produced 10 years earlier? Why does sh running-config display the options applied to a single interface in different parts of screen - it is totaly unrea