Document Types in CV03n  Hiding EXIT or BAPI

Hi ,
I have some document types in customizing . But in Transaction CV01n I want to display only some document types  in the F4 help .
Pleas let me know if there are some exits or some customizing can be done for the same .

Hi,
Take the search help and check if it has a search help exit and try to do modifications in it.
Thanks,
Venkatesh.

Similar Messages

  • Non PO invoice : Entry of document types

    Hi,
    I am working on SRM5.0 with EC scenario. Client needs to perform invoice / credit memo with document type.  We can’t select document type from drop down box at header level. How to replicate backend invoice document type (RE gross invoice, RN net invoice, etc) to SRM? Any report to execute for it?
    Thanks in advance.
    Rahul Mandale

    Hi Yann,
    Client need to create SRM invocie without PO but with different document type and should create corresponding accounting documents in backend.
    In SRM SPRO, it is mentioned that "For invoice verification, you can only set RE as the document type for posting gross in the backend system.You can also set another document type using a user exit in the backend. This also has to be flagged as gross document type."
    Which user exit will help here to get Idoc inbound parameter to create different document type RE, AE, AA etc. ?
    Let me know if you had came across such requirement.
    regards,
    Rahul Mandale

  • PO document types and user exit

    Hi freinds
    There is a typical issue I have. The Document types required by my client is huge. I want to bring them down. Is there any way it can be done using user exits. If yes how to do the same.
    Regards
    Eldee

    Hi Dev,
    To reduce the document types you have to delete those entries from customizing tables you need not have to use user exit for that
    Which document types you want to reduce?
    BR
    Diwakar

  • User Exit for PO Calculation Schema Determination by PO Document Type

    Hello,
    Due to complex pricing requirements for both standard inbound purchase orders and return to vendor purchase orders, we need two separate calculation schemas to be applicable to each vendor.
    I have configured the primary calculation schema (ZM1000) which is correctly calculated on our standard purchase orders.  Through ENHANCEMENT-POINT mepo_header_fill_neu_01 SPOTS es_saplmepo (program SAPLMEPO) we have implemented code to change the calculation schema to the return schema (ZM1002) if the document type is one of our return purchase order types.
    ENHANCEMENT 1  ZMEEI_PO_PRICE_SCHEMA_DETM.    "active version
    IF fekko-bsart eq 'ZR1' or fekko-bsart eq 'ZR2' or fekko-bsart eq 'ZR3' or fekko-bsart eq 'ZR4'  .
         fekko-kalsm = 'ZM1002'.
    ENDIF.
    ENDENHANCEMENT.
    We are facing an issue where once the data is correctly entered into the return PO and the pricing has been determined there are errors.  The following is observed in the pricing analysis:
    1)  The correct calculation schema is determined (ZM1002).
    2)  Pricing conditions which have a condition record under the main calculation schema (ZM1000), but which do not exist in the return one (ZM1002) still appear in the pricing.  This is an issue.
    3)  Price conditions which have a condition record under the new schema (ZM1002), and which should appear, receive the message "Condition record exists, but has not been set".  This is an issue.
    When the pricing is re-determined manually at the line item level, it recalculates correctly and issues 2 and 3 above are adjusted accordingly.
    Question:
    Is there something missing in our code above which is cause these issues or is there a better user exit we should be using to address this requirement?
    Thanks in advance!

    Melih
    What we ended up doing was using ENHANCEMENT-POINT item_process_main_01 SPOTS es_saplmepo (program SAPLMEPO) to re-price the line items automatically when processing.  This solved our issue.
    IF EKKO-BSART = 'ZR1' or EKKO-BSART = 'ZR2' or EKKO-BSART = 'ZR3' or
    EKKO-BSART = 'ZR4'.
    lf_ext_calctype = 'C'.
    ENDIF.

  • Purchase requisition document type- USER EXIT

    Hi,
    I want to create two separate document type for material and services for PR that is created from PS. What is the user exit I shall use for the purpose or any other way to do.
    Zinni

    Hi
    Check this link for user exit.
    http://sap.niraj.tripod.com/id21.html
    Thanks
    S.Murali
    Edited by: S. Murali on Jul 8, 2009 2:30 PM
    Edited by: S. Murali on Jul 8, 2009 2:30 PM

  • BAPI only assign Document Data(Document Number/Document Type) to Material

    Hi,
           Can any one tell me A Standard BAPI which is only assign(Not Create New Document Number)
           Document Data to Material Number.
    Regards
    Smruti

    Hi Ganesh,
    i am writing a Custome BAPI for Material Create uisng "BAPI_MATERIAL_SAVEDATA " and also i assign an Existing Document Number ,Document Type to the Material Number which is Created using "BAPI_MATERIAL_SAVEDATA".
    so, i need a one SAP Standard BAPI which is assign an Existing Document Number ,Document Type to Material Number and the Document number and Document type is available  Input Parameter of my Z BAPI.
    Note: Don't Create New Document Number i have docuemnt number and just assign to Material Number
    Thanks and Regards.
    Smruti

  • User exit for VA01 - No range for sales document type

    Dear Experts,
    In our project, we have 8 sales organizations and these are assigned to 8 different company codes. Actually our client doesnt want to maintain different document types for each Sales Organization. We need to maintain one document type for all the sales organizations and different No ranges for each sales organization. So can any one guide me on User exit available for this purpose.
    Thanks & Regards,
    Rahul

    hi,
    pls refer to the following user exit.
    Include prog : MV45AFZZ
    USEREXIT_NUMBER_RANGE
    Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
    The user exit is called up in the FORM routine BELEG_SICHERN.
    reg
    Deepak

  • Field Exit for Sales Document Type in VA01

    hi
       i want to do field exit for Sales Document Type in VA01.
    but i dont know to find the correct exit.
    pls tell the exit name and the steps to find it.
    thank u

    Hi,
    Goto this link u will get the information u required....
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9cd334f3-0a01-0010-d884-f56120039915
    Check the numerous threads that already exist in SDN :
    CMOD and SMOD
    http://www.sap-img.com/abap/what-is-user-exits.htm
    Regards,
    Manish

  • User Exit for MIRA to default document type

    Is there any user exit in MIRA ,which can change the default document type .Because normally the document type is defaulted in the customization ,all the user exits which are available have the incoming structure (INVFO) in which the document type(INVFO-BLART) is coming as IMPORT parameter (e.g.  EXIT_SAPLFDCB_001),hence it cannot be changed .
    I would like to default the document type based on company codes .
    Please let me know if there is any other way of doing this.

    >
    Rahul Saxena wrote:
    > I have given the condition"BSEG-ZTERM = 'ZTST'" in Prerequisite, and in the Substitutions when I try to assign  constant value '02/16/2009' to the field Baseline Date, I don't see that Baseline date field in Substitute fields for Class '009'.
    >
    > How do I add Baseline date in that popup to select and assign values.
    >
    > Please suggest.
    >
    > Thanks-
    i think your date format and system date format is not suitable.
    give the date format as 20090216 as system format.

  • New document type to be copied from old document type

    Dear Sir
    i have created one document in document type draw no i want to delete that document from draw and i have to copy its all document to my new docmuent type Z09 please guide how can i do it.
    regards
    kunal

    Hi Kunal,
    normally you cannot just change the document type for a document info record. So you have to create a new document info record of type Z09 and maintain the same data for it in transaction CV01N. Since this new document info record is created you can delete the older wrong document info record which is no longer used.
    Another possibility could be to use a DMS BAPI sequence. Here you can read out the whole data with BAPI_DOCUMENT_GETDETAIL2 from the initial document info record. Then you can hand over this data to BAPI_DOCUMENT_CREATE2 and change just the document type to Z09. At the end execute BAPI_TRANSACTION_COMMIT to create the new document info record in your database tables. Afterwards you should be able to see the new document in transaction CV03N as well with the same data.
    I hope this could be useful for you.
    Best regards,
    Christoph

  • Send some document and link to screen exit

    send [email protected]
    enhancement document
    Regarding
    anil

    this will give u clear picture.
    Screen Exit:
    How to implement screen exit for a SAP standard transaction
    Introduction
    SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
    To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
    To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
    An append structure in the database table with the new fields.
    A subscreen area into the standard screen – where the programmer can attach his subscreen of his own program with the new fields.
    A function group under which the new subscreen has to be created with the new fields.
    Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen – so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
    Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
    Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
    Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
    Pre-Requisites
    The developer to work on screen exit should have essential knowledge on the following:
    DDIC concepts, including the knowledge of append structure.
    Concept of SAP Enhancements and implementing them using Projects.
    Concept of function exits.
    Knowledge on Module Pool – including subscreens, Tabstrip controls etc.
    Steps
    Guidelines
    So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
    Find out the Required Enhancements
    Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton ‘SAP Applications’. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest – for e.g., Purchasing, Asset Accounting, etc.
    Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
    Utilize the Enhancement in a Project
    After you have found one, do as directed in the documentation. Generally, the steps are as follows:
    Create a project using CMOD including your enhancement.
    Create the append structure with new fields.
    Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
    Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
    Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
    Activate the project.
    Test to ensure that required functionality are met.
    Case Study 1
    Add three new custom fields for Asset master and maintain information for them
    Requirement
    Three fields in the legacy system have to be maintained in Asset master. These fields are:
    Original Asset number – 20 characters
    Location 2 – 15 Characters.
    Model no – 20 characters
    Location 2 should start with ‘L’.
    Pre-Analysis
    Finding out the Enhancement
    As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
    Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
    Studying the Function Exits
    The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
    EXIT_SAPLAIST_002
    Function module Level Documentation
    This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
    Import Parameters
    Understanding
    This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
    EXIT_SAPLAIST_003
    Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
    Understanding
    This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
    Studying the Documentation of the Enhancement
    The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
    Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
    Deciding the Final course of Action
    After making all the investigations, the final course of action was determined.
    SrlNo Step Justification
    A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
    Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
    A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be ‘CUST’ (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
    In the PAI of the subscreen, validation for Location to start with ‘L’ will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
    In the custom include of the function exit module ‘EXIT_SAPLAIST_002’, the following code will be written:-
    ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
    In the custom include of the function exit module ‘EXIT_SAPLAIST_003’, the following code will be written:-
    E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
    Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done – otherwise, the new custom subscreen will not be displayed in the Asset master screens.
    Development
    Creating a Project to include the enhancement
    Go to transaction CMOD and create a project.
    Enter a description for the project. Then, click on the pushbutton ‘Enhancement Assignments’ in the Application Toolbar.
    Enter the name of the enhancement and Save.
    Go to ‘Components’.
    Creating Custom Include for ANLU
    The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
    Create the include structure with three new fields, as required. Then, save and activate it.
    Develop the subscreen and the program
    Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
    Create it as subscreen.
    Then, go to the Layout of the screen and create three new fields from Database table ANLU.
    Drag the fields in the screen body and place them.
    Then, save and activate the screen and come back to screen flow editor.
    Create the PAI module to add validation for field “Location 2”, as required .
    Activate the whole function group and come out.
    Write code in the Function Exits to synchronize the programs
    Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
    Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
    Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
    Then, activate everything – the whole project and come out.
    Complete the configuration to link the subscreen
    The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
    Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
    Here, the requirement is to create these three custom fields in the tab page ‘General’ of asset master screen ( AS01/AS02/AS03/AS91).
    Determine the Layout
    To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class ‘1000’ and click on folder ‘General Assignment of Layout’.
    Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout ‘SAP’ cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
    Create new tab layout
    Go to transaction AOLA. Copy the tab layout ‘SAP’ to create another layout, say, YSUB.
    System will copy all the settings and will inform you about that.
    Select your newly created layout and double-click on the folder ‘Tab page titles’.
    You want to put your custom fields in the tab page “General”. So, select this tab page entry and double-click on the folder "Position of Groups".
    Here, all the field groups currently residing in the tab-page “General” are shown. Add an entry for your newly created fields.
    Select the group box from the list. An entry will come with “U” padded with the custom subscreen prepared by you.
    Then, save and come out.
    Assign the new Layout to Asset Class
    Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
    Save and come out.
    Test the Exit
    Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to them…save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
    Original Source: ittoolbox.com
    User Exits:
    User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
    The naming standard of function modules for functionmodule exits is:
    EXIT_<program name><3 digit suffix>
    The call to a functionmodule exit is implemented as:
    CALL CUSTOMER.-FUNCTION <3 digit suffix>
    To find a Exit.
    Goto Transaction -- Find The Package
    SMOD >f4>Use the Package here to Find the Exits In the Package.
    Else if you Want to search by Application Area wise ,
    There is one more tab to find the Exits in the Respective Application Area.
    Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
    Now Run ur Transaction to Check if it Triggers.
    Thats it..
    Suppose you need to find out all the user exits related to a tcode.
    1. Execute the Tcode.
    2. Open the SAP program.
    3. Get the Development Class.
    4. Execute Tcode SE84.
    5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'
    6. Enter the Development class and execute.
    Check out this thread..
    The specified item was not found.
    1. Type the transaction : system->status-> <PROG. NAME>
    2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.
    3. Open CMOD utilities->SAP enhancements
    EDIT->All selections
    4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.
    5. The displayed list contains the enhancements names for the transaction You were looking for.
    6. Create a project in CMOD and the code in default include->activate.
    http://www.erpgenie.com/sap/abap/code/abap26.htm
    which gives the list of exits for a tcode
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
    For information on Exits, check these links
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sapgenie.com/abap/code/abap26.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    http://www.easymarketplace.de/userexit.php
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    http://www.planetsap.com/userexit_main_page.htm
    User-Exits
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sap-img.com/ab038.htm
    http://www.planetsap.com/userexit_main_page.htm
    http://www.sap-basis-abap.com/sapab013.htm
    http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283
    These links will help you to learn more on user exits.
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
    http://www.planetsap.com/userexit_main_page.htm
    http://www.allsaplinks.com/user_exit.html
    www.sap-img.com/abap/what-is-user-exits.htm
    Also please check these threads for more details about user exits.
    Re: Screen exit
    user exit and customer exit
    user exit
    1. Document on UserExits in FI/CO
    http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
    2. Finding User Exits...
    http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits
    3. List of all User Exits...
    http://www.planetsap.com/userexit_main_page.htm

  • PO Document Type for Free Goods only

    Good day,
    Business Scenario: Client wants to track FreeGoods made. To solve this, we have created PO document type "Free Goods PO"
    Current: I choose Free Goods PO, input materials and then tick the FG indicator.
    Question: Is it possible that for this document type, every material I put, the indicator is automatically ticked? And that only free goods can be placed in this document type?
    Thank you,
    Simon

    Simon,
    You will need someone with a developer key to be able to implement the code.  However, in the main PO processing program SAP has created spots where customers can add custom code for situations like this. 
    If you go to transaction SE81, you can select the MM module.  From there click the "Select subtree +/-" button (will highlight MM in yellow).  After that click "Information System".  This will bring you to the developer workbench where you can review all of the enhancement spots and user exits in the MM module.
    If you expand Enhancements, and click on Enhancement Spots, a selection screen should appear to the right.  In enhancement spot enter 'es_saplmepo' and execute.  Double click on the enhancement spot.  That will produce the list of all of the enhancement points within that main program.  There are ones specific to the header fields as well as item fields.
    If you scroll down to "item_process_main_01" and double click it will bring you into the code where the above if statement can be added (for some reason it doesn't bring be right to the item_process_main_01 spot so i have to scroll to find it).
    As the program is running it will hit your enhancement and process that as it is going.  A developer can provide more details.
    Hope this helps,
    Matt

  • FI-CA document type when a print document is created

    Hello everybody,
    We have been searching events (e.g. 0061)/user-exit to change the FI-CA document type when a print document (based on our own logic) is created with transaction EASIBI without success. Maybe you have enhanced something in another project. Can you share you experiences?
    Thanks in advance.
    Fernando.

    We have enhanced event R999.

  • Questions on SAP Document Type

    Question 1: I want to create document name for a document type as characters like ABC for a document type SEP, so that the final DIR looks like SEP-ABC-000-00 (for example), how do I do the same.  It is only taking internal or external number range which is only numerical.

    Hi Paddy,
    In DC10 Transaction you need to select the Number Assignment as "Internal or External with Exit"  then you will be able to give whatever you want as the DIR with Alphacharacters even, But if you want to build a relation then, you need to wirte a exit on Number Exit field in DC10 itself.
    Regards
    Rehman

  • PO Item Goods Receipt indicator change based on the PO document type

    Hi All,
    Our requirement is for a particular PO document type the PO Item Delivery tab > goods receipt indicator needs to be set as blank and the field should be greyed.
    For this PO type we are usign the account assignment category K and F. We cannot remove the Goods receipt indicator from this account assignment in SPRO because this is the central change and it will affect other Purchase organizations.
    We are using the R3 4.6c Version.
    We tried the User Exit "MM06E005" with exit FM "EXIT_SAPMM06E_016" but this cannot be used to changed the PO Item standard fields.
    Badi ME_PROCESS_PO_CUST not exist in R3 4.6c.
    Is there any other solution avl to meet out requirement.
    Thanks & regards.
    Madhan.

    Hi,
    I think you have posted the question in the wrong Forum.

Maybe you are looking for