Adding 'Your Reference'(VBKD-IHREZ) field to Field catalog in Output determ

The requirement is maintaining the condition table using Sales Org/Sales Doc Type/Your reference in output determination process. But the field 'Your reference(VBKD-IHREZ)' is not in the field catalog. Can someone tell me how to add the VBKD-IHREZ to field catalog?
Thanks in Advance.

Hey,
You can find intructions for adding fields to field catalog from this link: http://www.sap-basis-abap.com/sd/how-to-add-new-fields-to-field-catalog.htm

Similar Messages

  • How to add a field VBKD-IHREZ to field catalog in Output determination?

    The requirement is maintaining the condition table using Sales Org/Sales Doc Type/Your reference in output determination process. But the field 'Your reference(VBKD-IHREZ)' is not in the field catalog. Can someone tell me how to add the VBKD-IHREZ to field catalog?
    Thanks in Advance.

    Hi
    See SAP Note 21040 - Allowed Fields not appearing for condition table
    Regards
    Eduardo
    PD: I forgot, go to IMG and see the documentation in the path: SD/system modifications / create new fields  (using cond.tec) / new fields for output control and read the documentation. It tells us structures and how to populate (exits)
    Edited by: E_Hinojosa on May 6, 2011 5:48 PM

  • User exit to modify EKKO-IHREZ ( Your reference field )

    Hi All,
    We are using Badi ME_PROCESS_PO_CUST to modify You reference ( EKKO-IHREZ ) field during purchase order creation . This badi is called when purchase order is created  through ME21N and when PO is created through BAPI . This badi is not called when PO is created through ME21 .
    Can you please let me know if there is any other user exit/ badi ( or any other way ) where we can modify EKKO-IHREZ when PO is created through ME21 . I checked few user exits but all are having EKKO as the Importing parameter so changes  made to IHREZ  will not be reflected .
    Thanks and Regards,
    Kiran.

    Hi,
    Have you tried with BTE function modules, try using "01000730     APO Plug-In: Purchase Order" Event, only you have to enter BERE transaction, execute with F8, locate 01000730 event, select it and then press "Sample Function Module" button, copy the function module sample "SAMPLE_INTERFACE_01000730" by your own ZFUNCTION where you will have the posibility to make changes to EKKO-IHREZ field see the parameters you can acces and make all the programming you need like:
    FUNCTION ZSAMPLE_INTERFACE_01000730.
    ""Local Interface:
    *"  IMPORTING
    *"     VALUE(I_EKKO) LIKE  EKKO STRUCTURE  EKKO OPTIONAL
    *"     VALUE(I_CALL_MRP) DEFAULT ' '
    *"  TABLES
    *"      T_XEKPO STRUCTURE  EKPO OPTIONAL
    *"      T_XEKET STRUCTURE  EKET OPTIONAL
    *"      T_XEKKN STRUCTURE  EKKN OPTIONAL
    *"      T_YEKPO STRUCTURE  EKPO OPTIONAL
    *"      T_YEKET STRUCTURE  EKET OPTIONAL
    *"      T_YEKKN STRUCTURE  EKKN OPTIONAL
    ToDo
    I_EKKO-IHREZ = 'MY_IHREZ_VALUE'.
    ENDFUNCTION.
    Activate it.
    Then go to transaction FIBF, then go to menu "Settings->Process Modules->...Of an SAP Application", once there create a new entry and set 01000730 for the process and your ZFUNCTION name in the Function Module Field, save changes and make a test to see if it works fine.
    I hope it helps.
    Regards,
    Moises Grappin.

  • ISA order.jsp; message and validation for "Your reference" field

    Hi Everyone,
    I am new to ISA and working on java program to add message to "Your Reference" field in order.jsp page if this field is empty and clicked on "Check Out" button and user need to remain in the same page until user enters information in this field.
    Message is available in .xlf file.
    Please suggest me where to write this code for both message and validation for this field.
    Thanks in advance
    Prasad

    I fixed the requirement
    thanks
    Prasad

  • Return order - your reference field is grey

    hi,
    I want to make use the field "your reference" in item -->  PO tab --> your reference. however, this field is grey in return order. how can I make it changable. Thanks

    Hi
    Normally this field is not grayed out. Check field varient with help of SHDO. In order to copy PO number from order to return order you will have not create copy control routine with help of T code VOFM. Standard routine is 101. Copy and modify routine according you need and assing the new routine in copy controls between OR to RE.
    Vijay

  • Your reference field in B2B shop

    Hi
    Can anyone explain, what is the importance of field
    Your Reference
    in B2B webshop while creating orders.
    Regards,
    Ajay

    Hi,
    Users use this for their reference to the particular order. Its just for the name sake to remember the order if they forget the order no.
    It has got nothing significance in Order processing. It is only for the benefit of the user.
    Regards,
    Sateesh Chandra

  • Need help with BBP_CUF_BADI - Adding your own screens for custom fields.

    We are on SRM 5.0 and we need your help to add the custom fields to a separate screen.
    All the item level custom fields are visible in Item Details screen under Basic Data and Header level custom fields are visible under Additional Specifications. Instead we like to add a new Tree as Custom fields just like Basic data or Cost Assignment in item details screen.
    The documentation for the BADI BBP_CUF_BADI does not say how to include a new tree structure. I did everything mentioned in the BADI like creating a screen and two funciton modules and generating the template. But it does not work. Any help is greatly appreciated.
    I went through other threads on this forum. So please do not waste your time pointing me to the old threads.
    Please provide sample code if possible.
    Thanks
    KM

    It seems that you are looking for exact solution but many a times you get pointers on this forum which lead you in correct direction.
    I have heard from one project site that they are able to fulfill the requirement via creating a webdynpro and linking the same to user role.
    if this doesn't help, just ignore.
    BR
    Dinesh

  • EDI-IDOC: want to generate Reference Specifications for Bank Details field

    Hi Guru,
           We are running to the situation that we use EDI with China vendor (using China bank account). The bank account for China has greater than 18 characters which is the maximum limit for bank account field. Based on note 96624, we are suggested to maintain the exceeding amount into the "Reference Specifications for Bank Details" field. However, when I run the payment on F110, IDOC do not generate the reference field.
           How can the bank reference field be included in the IDOC?
    Thanks,
    Song

    Hi Auro,
    You use use EDI_DC-SNDSAD field, currently this field is used no where.
    If you not sure where to see double control record and click address info tab
    you can use either field receiver or sender.
    For testing use WE19 transaction and pass your paymethod to following field
    and then inform to EDI Mapper that your sending paymethod in this field.
    For them this field is very easy to grab.
    Let me know if you any concern.
    Thanks,
    Narayan

  • Adding field in standard SAP transaction output results.

    Hi,
    I have to add a new field in standard SAP transaction output results.
    Can any one tell me what are the ways (brief explanation) that I can do this?
    If using exists - then what kind of exists I have to use? And how to find out the possibility with user exists?
    Thanks for your time.
    Thanks.
    Chris.

    Hi,
        There are so many ways to find out the user exits.
    Hi,
    To see SAP Exits -> Use Tcode SMOD
    To See create a project for Customer Exits -> Use Tcode CMOD
    There are projects to which Exits are assigned. Selects the relevant projects.
    What is User Exit:
    http://www.sap-img.com/abap/what-is-user-exits.htm
    How to find then:
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    All Exits List:
    http://www.easymarketplace.de/userexit.php
    Do a search on SAP Exits, Customer Exits, enhancements, etc
    Step 1 :- Execute transaction
    step 2 :- Click on Status Menu
    step 3 :- Double click on the program (screen) __?????___
    Step 4 :- Search source code for the 'Customer-Function' string using the find button. Remember to select 'In main program'.
    Step 5 :- A list of search results should be displayed indicating where all function exits can be found.
    You can now double click on each of them to go to its position in the source code. This also
    allows for the insertion of breakpoints so that you can test if the exits are called in the
    appropriate place.
    Step 6 :-Once you have found the Function Exit within the source code (Find Function Exit) you need to
    access the actual function module it executes. This is done using the following steps:
    Step 6.1 :-
    Step 1
    Locate desired 'Call Customer-function' statement within source code.
    Step 2
    If code is not within main program (module pool) e.g. SAP* then you will need to find this
    out by selecting 'Main Program' from the 'GOTO' menu. The Main program for transaction
    Step 3
    The actual function module name can now be calculated based on the information retrieved,
    it is defined by the following format:
    EXIT_<Program name>_<Exit number>
    eg :- 'EXIT_SAPLMR1M_004'.
    Step 7.1:-
    Once you have found the Exit function module
    Step 1
    Execute transaction CMOD
    Step 2
    Select 'SAP Enhancements' from the 'Utilities' menu.
    Step 3
    Select 'All selections' from the 'Edit' menu.
    Step 4
    Now populate the Component name field with the exit function module and press
    the execute button.
    Step 5
    A list of all Exits(Enhancements) containing that function module should now be displayed.
    Step 5
    You can now double click on the desired exit to display a detailed description of its uses and a list of all
    components contained in it.
    Implementing Function Exit
    This is required in-order to activate Function exit:
    Step 1
    The first step is to enter source code into function module in the usual way i.e. via SE37.
    There will already be an include declaration within the code with the following
    format: Include zx*.
    Double click on this to create it, source code can then be entered within here.
    Although it is good practice to create another include with this to store your
    code, this allows separation of difference enhancements allowing them to be easlity
    removed without de-activating the enhancement.
    Step 2
    Execute transaction CMOD and create new Enhancement. Enter name and press the create
    Button.
    Step 3
    The following screen should be displayed, enter short text then click on the 'Enhancement
    Step 4
    Now enter the Exit name (enhancement) which contains the desired Function Exit.
    Step 5
    Return to initial screen of CMOD and press the activate icon. The exit is now ready for use.
    Please Mark The Helfull Answers & close the thread.
    regards
    dj
    reward for all useful answers.

  • Adding new field in the table for Output

    Hi ,
    I need to add a field catalogue as Payment method in the condition table for Output, but the payment method field does not exist in the table. Can this be done?
    regards,
    Ragu

    Hi Refer below link on sdn for adding new Field
    Adding New Field to Catalog
    Adding New fields to field catalog

  • Adding fields in condition table for output control

    Hello,
    I have added a new field LGNUM in the fieldcatalog for delivery in transaction VOK2.  Now i need to create a new condition table in which i want to include this field. But i am not able to see LGNUM in the list of fields which are displayed in the field list.
    Please advice.
    Thanks in advance,
    Mathangi

    Hi Refer below link on sdn for adding new Field
    Adding New Field to Catalog
    Adding New fields to field catalog

  • Need your assistance in mapping Structure and Field in DME Tree

    Hello Friends - I need your help in "Mapping from structure field" in DME.
    In the existing format tree, It is mapped Structure as "FPAYP" and Field name "BNAME" to populate Company Code name in the Payment file.
    Now I am asked to change this to populate value either from OX02 or OX15.
    When Company Code name was maintained, It was maintained in short and in the address tab, Full name is maintained.
    Please let me know which Structue and Field I should assign to pull the value either from OX02 or OX15.
    Thanks for your help.

    Thanks a lot Henri/Lakshmi.
    I have maintained mapping procedure Sturecture/field - FPAYHX/AUST1 to get the CoCd name in the file. In AUST1, Length of the CoCd is more  than 18, and as per Bank format, It should be 18 characters in length.
    User is not happy that complete CoCd name is not populated in the file. He has come up with an alternative and shortened the CoCd name that needs to be populated in the file and suggested us to get the value into the payment file. We should not replace CoCd name with the name he suggested in OX02/OX15,FBZP.
    My doubt is that if there is any filed I can use to maintain the name he suggested and assign it in mapping procedure.
    Thanks

  • New field in field catalog in output

    How can I add new field in field catalog in Output determination. I heard it can be done through a user exit. Can somebofd help with the user exit name.

    if you want to use new field in output determination - you need to modify corresponding communication structure (KOMKBV1 - header structure for V1 application - like sales orders, contracts,...)
    Then in RVCOMFZZ in one of the userexits you can populate those fields.
    After your fields are added to KOMKBV1 - you can use them in output determination.

  • Field Symbols, Field String, and Field Group.

    Hi,
    Can you differentiate between filed symbols, field strings and field groups,
    With regards,
    Bharath Mohan B

    Hi,
    Field Symbols
    Field symbols are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
    Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
    Field symbols are similar to dereferenced pointers in C (that is, pointers to which the content operator * is applied). However, the only real equivalent of pointers in ABAP, that is, variables that contain a memory address (reference) and that can be used without the contents operator, are reference variables in ABAP Objects.
    All operations programmed with field symbols are applied to the field assigned to it. For example, a MOVE statement between two field symbols moves the contents of the field assigned to the first field symbol to the field assigned to the second field symbol. The field symbols themselves point to the same fields after the MOVE statement as they did before.
    You can create field symbols either without or with type specifications. If you do not specify a type, the field symbol inherits all of the technical attributes of the field assigned to it. If you do specify a type, the system checks the compatibility of the field symbol and the field you are assigning to it during the ASSIGN statement.
    Field symbols provide greater flexibility when you address data objects:
    If you want to process sections of fields, you can specify the offset and length of the field dynamically.
    You can assign one field symbol to another, which allows you to address parts of fields.
    Assignments to field symbols may extend beyond field boundaries. This allows you to address regular sequences of fields in memory efficiently.
    You can also force a field symbol to take different technical attributes from those of the field assigned to it.
    The flexibility of field symbols provides elegant solutions to certain problems. On the other hand, it does mean that errors can easily occur. Since fields are not assigned to field symbols until runtime, the effectiveness of syntax and security checks is very limited for operations involving field symbols. This can lead to runtime errors or incorrect data assignments.
    While runtime errors indicate an obvious problem, incorrect data assignments are dangerous because they can be very difficult to detect. For this reason, you should only use field symbols if you cannot achieve the same result using other ABAP statements.
    For example, you may want to process part of a string where the offset and length depend on the contents of the field. You could use field symbols in this case. However, since the MOVE statement also supports variable offset and length specifications, you should use it instead. The MOVE statement (with your own auxiliary variables if required) is much safer than using field symbols, since it cannot address memory beyond the boundary of a field. However, field symbols may improve performance in some cases.
    check the below links u will get the answers for your questions
    http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3860358411d1829f0000e829fbfe/content.htm
    http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/field_sy.htm
    http://searchsap.techtarget.com/tip/1,289483,sid21_gci920484,00.html
    Syntax Diagram
    FIELD-SYMBOLS
    Basic form
    FIELD-SYMBOLS <fs>.
    Extras:
    1. ... TYPE type
    2. ... TYPE REF TO cif
    3. ... TYPE REF TO DATA
    4. ... TYPE LINE OF type
    5. ... LIKE s
    6. ... LIKE LINE OF s
    7. ... TYPE tabkind
    8. ... STRUCTURE s DEFAULT wa
    The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Untyped Field Symbols ad Cannot Use Field Symbols as Components of Classes.
    Effect
    This statement declares a symbolic field called <fs>. At runtime, you can assign a concrete field to the field symbol using ASSIGN. All operations performed with the field symbol then directly affect the field assigned to it.
    You can only use one of the additions.
    Example
    Output aircraft type from the table SFLIGHT using a field symbol:
    FIELD-SYMBOLS <PT> TYPE ANY.
    DATA SFLIGHT_WA TYPE SFLIGHT.
    ASSIGN SFLIGHT_WA-PLANETYPE TO <PT>.
    WRITE <PT>.
    Addition 1
    ... TYPE type
    Addition 2
    ... TYPE REF TO cif
    Addition 3
    ... TYPE REF TO DATA
    Addition 4
    ... TYPE LINE OF type
    Addition 5
    ... LIKE s
    Addition 6
    ... LIKE LINE OF s
    Addition 7
    ... TYPE tabkind
    Effect
    You can define the type of the field symbol using additions 2 to 7 (just as you can for FORM parameters (compare Defining the Type of Subroutine Parameters). When you use the ASSIGN statement, the system carries out the same type checks as for USING parameters of FORMs.
    This addition is not allowed in an ABAP Objects context. See Cannot Use Obsolete Casting for FIELD SYMBOLS.
    In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs. See Defining Types Using STRUCTURE.
    Effect
    Assigns any (internal) field string or structure to the field symbol from the ABAP Dictionary (s). All fields of the structure can be addressed by name: <fs>-fieldname. The structured field symbol points initially to the work area wa specified after DEFAULT.
    The work area wa must be at least as long as the structure s. If s contains fields of the type I or F, wa should have the structure s or at least begin in that way, since otherwise alignment problems may occur.
    Example
    Address components of the flight bookings table SBOOK using a field symbol:
    DATA SBOOK_WA LIKE SBOOK.
    FIELD-SYMBOLS <SB> STRUCTURE SBOOK
    DEFAULT SBOOK_WA.
    WRITE: <SB>-BOOKID, <SB>-FLDATE.
    Related
    ASSIGN, DATA
    Additional help
    Declaring Field Symbols
    FIELD GROUPS
    are used to hold/handle large amount of data when the internal table are not useful
    we use EXTRACT statement, HEADER structure in them
    see the example
    REPORT demo_extract.
    NODES: spfli, sflight.
    FIELD-GROUPS: header, flight_info, flight_date.
    START-OF-SELECTION.
      INSERT: spfli-carrid spfli-connid sflight-fldate
                INTO header,
              spfli-cityfrom spfli-cityto
                INTO flight_info.
    GET spfli.
      EXTRACT flight_info.
    GET sflight.
      EXTRACT flight_date.
    END-OF-SELECTION.
      SORT STABLE.
      LOOP.
        AT FIRST.
          WRITE / 'Flight list'.
          ULINE.
        ENDAT.
        AT flight_info WITH flight_date.
          WRITE: / spfli-carrid , spfli-connid, sflight-fldate,
                   spfli-cityfrom, spfli-cityto.
        ENDAT.
        AT flight_date.
          WRITE: / spfli-carrid , spfli-connid, sflight-fldate.
        ENDAT.
        AT LAST.
          ULINE.
          WRITE: cnt(spfli-carrid), 'Airlines'.
          ULINE.
        ENDAT.
      ENDLOOP.
    FIELD STRING is nothing but a string with  one row of records.
    Reward points if useful
    regards
    Anji

  • New field on field catelogue

    Hi
    For a discount condition type I want to create a new condition table with a filed which is not in filed catelogue. So what and all the entire procedure I have to do.
    thns & rgds
    raju

    Hi,
    Please find below the information how to add a new field to the field catalogue Ex. Profit center is the new field i wish to add, then
    For adding field into Field catalogue:
    you should first identify the field for Profit Center (Design ID) and then do as follows:
    For example if you want to use field PSTYV ('Sales document item category') that is included in structure KOMP ('Pricing Communication Item') as a key for a condition table.
    When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.
    Prerequisites:
    For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition Structures').
    To solve the problem, proceed as follows:
    1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, 'ZZ - sales document item category' and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.
    2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:
    Component   Component type
    ZZPSTYV     ZZPSTYV
    Save, check and activate the change you made.
    3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.
    4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control' and execute 'Define Condition Tables'. Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.
    5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.
    6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:
                  MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
    In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.
    Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.For header fields, use structure
    KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead of USEREXIT_PRICING_PREPARE_TKOMP.
    For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition
    Technique) -> New Fields for Pricing' and Note 21040.
    For creating a condition Table:
    1) There are almost all the regularly used Conditon Table predefined in the system from 001 to 500.
    See what best you can use the Standard Tables to avoid further errors.
    2) In case you should define the new condtion Table,
    a) Goto TCode: V/03
    b) Give a Table any number from 501-999
    Press execute and reach to next screen.
    c) Check up whether  the field you are looking is already added in Field catalogue.
    d) Double click on the fields you want to make a Table..one by one. Note that the sequence here is important in higher hierarchical to lower..
    Eample : Sales Org, DC, Division, Customer and then Material etc..,
    e) After selecting, click on the Techincal View buttin (redone) and reach to next screen.
    7) Check which key  should be in header and which key should be footer. Use check and uncheck functionalities there..
    8) Once you are through with all the above steps ..click on generate button.
    Check the Table is generated or not.
    You can check it at V/04 or V/05 or in SE11.
    Regards,
    Ravi Duggirala
    Edited by: ravi duggirala on Jun 9, 2008 10:48 AM

Maybe you are looking for