Modification in MEDRUCK for purchase order, RFQ, scheduling agreement.....

Hi all
I have requirment in which i have to modify standard script MEDRUCK for PO, RFQ, SCHEDULING AGREEMENT, AND QUANTITY CHART.
I know how to modify standard layouts but after modifying layouts what to do next??
How can i use same medruck script for RFQ, SCHEDULING AGREE, AND QUANTITY CONTRACT.
help me out!!!!!!!!!!

hai manisha,
Actually SAP Clubbed all the requriments And Made one FORM for one bussiness scenario.
So Depending On The Transaction That We Are Running System Will Automatically Triggers Particular Type.
So Take A Copy Of Medruck For Each Document That U have To Do.
Then Run Respective Transactions Then According to that configure NACE.
In NACE transaction, We will assign the Form name and the driver program name and the corresponding routine to be triggered in the driver program.
We should be able to tell the system to pick up the desired form layout and trigger the routine and get the data from the database and put it on to the form. All these stuff the system will come to know from the NACE settings.
NACE is used to create output type while creating the output type you will mention forms, and driver program.
that will be maintained in the table TNAPR.if you create the output type using NACE then it will be automatically visible in table NAST and TNAPR.
so check in NAST, TNAPR table
You can view all forms and driver programs for standard SAP Scripts.
Assigning Form and Driver proram to an Output type is as follows.
1) Go to NACE transaction
2) Select an Applicatin(V1-Sales,V2-Shipping,V3-Billing)
3) Click on Outputtypes Button
4) Comes to Change Mode
5) Click on New Entries button
6) Specify Output type,Form name and Program and Save it.
Check these links
/people/venkata.ramisetti/blog/2006/09/21/configuring-output-types-for-pdf-based-print-forms
http://help.sap.com/saphelp_erp2005/helpdata/en/c8/1989fe43b111d1896f0000e8322d00/frameset.htm
Condition records in NACE?
IF Found Helpfull Do Reward.
Regards.
Eshwar.

Similar Messages

Report for purchase requisition, purchase order and schedulling agreement.

Hi, thanks for your help.
I need a report or query just to view in one screen the related docs. as purchase requisition, purchase order and schedulling agreement.
I don´t know if there is a table or trx. with that information.
Is it possible to get that information via query ?
Thanks for your help.
Regards.

For PR and PO you can use ME5A
For PR and Scheduling agreements also you can use ME5A.

Difference between Purchase Order and Scheduling Agreement

Can any one explain the main differences between a Purchase Order and a Scheduling Agreement?
Thanks in advance

Hi,
A Purchase Order is a document that is given to Vendor to indicate our intention to buy goods from them. It contains what is the desired goods, how much quantity, price, and the delivery date, among other things.
A standard procurement cycle for this is:
PR --> PO --> GR --> IV
A Scheduling Agreement however, is a type of an Outline Agreement. Outline Agreements are divided into 2, first one is Contracts and second is Scheduling Agreement. So this is basically a long term agreement with a particular vendor that contains details on what is the desired goods, quantity, and the exact delivery dates.
A standard cycle for this is:
PR --> Create Scheduling Agreement --> Maintain Delivery Schedule (agreed dates on when vendor will send the goods and time) --> GR --> IV
As you can see, for Scheduling Agreement, PO is not required, but instead we would need to Maintain Delivery Schedule.
Just to share on Contracts, it appears as below:
PR --> Contract Creation --> PO --> GR --> IV
Regards,
Nazrin

Forms for Purchase order and Outline agreement

In my previous work which was in 4.7, smart tables and of course with the in-house development were used in order to activate country specific functionalities in P2P forms, such as PO, contracts, SA and RFQ printouts.
This functionalities are usually language, paper size and the content like specific country address, logos, tax display, etc.
So, the question is if the 6.0 version has any sort of localization or part of it for all or some countries that we can us as a base?

No such specific settings were introduced in ECC6.0.
Better proceed with customized Forms only
Umakanth

Goods-Receipt Block for Purchase Order depending on Goods-Receipt Date

Hi,
I want to set up the system so it can block the Goods-Receipt for Purchase Order respectively Scheduling Agreement if the Goods Receipt is about to take place 30 days or more before the Desired Delivery Date.
For Example: If I have a Purchase Order with the desired delivery date 30.09.2008. I want to set up the system so, that it bans (forbids) the Goods Receipt before the 01.09.2008.
If possible I would want to do that without additional programming. Is it possible to set up the system using only customising settings?
Thanks for your help
Bogdan

Hello Marius-Bodgan,
as this question is marked answered I assume you have received an solution for your requirement. Could you please share the solution with me by posting it here? I have the same requirement and did not find any possibility to do this in customizing.
Thanks in advance,
Emanuel
Found the solution in thread Re: Goods Receipt
Edited by: Emanuel Penalver on Jul 15, 2008 11:48 AM

Updating Scheduling data for Purchase Order

Hi,
I need a function module which can update the scheduling data for purchase order in EKET table. Normally we create Purchase Order as a reference from purchase requisition through BAPI_PO_CREATE1. That time it takes care of all the scenarios. But as per the requirement I want to create a PO which is created from more than one Purchase Requistions so I can't use the said BAPI. But still I am using this BAPI and after creation is completed I am updating the Requistions. The same scenario is taken care in ME59N, but I can't copy that code because of some requirements. So could any one please give me the idea to replicate the same functionality with any function module or other ways.
Thanks
Somnath paul

try to pass all u sheduling related fields to POSCHEDULE and make sure u have enabled POSCHEDULEX along with sheduling related fields .....also (if no changes are there leave it with space )...
this will definetly update not only eket table ....it will update every table regarding to purchase order,ekpo,ekko,eket ...etc
Example of population of BAPI interface in the Function
Parameter: POHEADER
COMP_CODE            =                    1000
DOC_TYPE             =                    NB
ITEM_INTVL           =                    00001
VENDOR               =                    0000001000
PMNTTRMS             =                     0001
PURCH_ORG            =                     1000
PUR_GROUP            =                     001
CURRENCY             =                     EUR
Parameter: POHEADERX
COMP_CODE            =                     X
DOC_TYPE             =                     X
ITEM_INTVL           =                     X
VENDOR               =                     X
PMNTTRMS             =                     X
PURCH_ORG            =                     X
PUR_GROUP            =                     X
Parameter: POITEM
PO_ITEM              =                     00001
MATERIAL             =                    100-100
PLANT                =                    1000
STGE_LOC             =                    0001
QUANTITY             =                    15.000
TAX_CODE             =                    V0
ITEM_CAT             =                     0
ACCTASSCAT           =                    K
Parameter: POITEMX
PO_ITEM              =                    00001
MATERIAL             =                    X
PLANT                =                    X
STGE_LOC             =                    X
QUANTITY             =                    X
TAX_CODE             =                    X
ITEM_CAT             =                    X
ACCTASSCAT           =                    X
Parameter: POSCHEDULE
PO_ITEM              =                    00001
SCHED_LINE           =                    0001
DELIVERY_DATE        =                    02.12.2002
QUANTITY             =                    6.000
PO_ITEM              =                    00001
SCHED_LINE           =                    0002
DELIVERY_DATE        =                    03.12.2002
QUANTITY             =                    5.000
PO_ITEM              =                    00001
SCHED_LINE           =                    0003
DELIVERY_DATE        =                    04.12.2002
QUANTITY             =                    4.000
Parameter: POSCHEDULEX
PO_ITEM              =                    00001
SCHED_LINE           =                    0001
PO_ITEMX             =                    X
SCHED_LINEX          =                    X
DELIVERY_DATE        =                    X
QUANTITY             =                    X
PO_ITEM              =                    00001
SCHED_LINE           =                    0002
Parameter: POACCOUNT
PO_ITEM              =                    00001
SERIAL_NO            =                    01
QUANTITY             =                    15.000
GL_ACCOUNT           =                    0000400000
COSTCENTER           =                    0000001000
CO_AREA              =                    1000
Parameter: POACCOUNTX
PO_ITEM              =                    00001
SERIAL_NO            =                    01
QUANTITY             =                    X
GL_ACCOUNT           =                    X
COSTCENTER           =                    X
CO_AREA              =                    X
Parameter: POCOND
ITM_NUMBER           =                    000001
COND_ST_NO           =                    001
COND_TYPE            =                    PB00
COND_VALUE           =                    79.900000000
CURRENCY             =                    EUR
CURRENCY_ISO         =                    EUR
COND_UNIT            =                    KG
COND_P_UNT           =                    1
CHANGE_ID            =                    U
Parameter: POCONDX
ITM_NUMBER           =                    000001
COND_ST_NO           =                    000
ITM_NUMBERX          =                    X
COND_TYPE            =                    X
COND_VALUE           =                    X
CURRENCY             =                    X
CHANGE_ID            =                    X
Parameter: POPARTNER
PARTNERDESC          =                    OA
LANGU                =                    EN
BUSPARTNO            =                    0000001100
PARTNERDESC          =                    GS
LANGU                =                    EN
BUSPARTNO            =                    0000001200
PARTNERDESC          =                    PI
LANGU                =                    EN
BUSPARTNO            =                    0000001000
reward points if helpful....

Open items for purchase order its very urgent

hi
my requirement is to write extract program for purchase order(me21) to extract only open items.
please provide sample code its very urgent.
thanks in advance.
points will be rewarded.
thanks
hari prasad reddy

check the below report :
REPORT ZMM_OPEN_PO_REPORT no standard page heading
 line-size 255
 message-id zwave.
======================================================================
Program Name : ZMM_OPEN_PO_REPORT *
Description : This report displays all Open PO Items and output *
 would be PO Number,Material number and so on *
Author : Seshu *
Date : 01/24/2007 *
MODIFICATION HISTORY *
DATE | AUTHOR | CHANGE # | DESCRIPTION OF MODIFICATION *
--|||--
01/24/07| Seshu | DEVK921979 | Initial *
D A T A D E C L A R A T I O N P A R T ***
type-pools
type-pools : slis.
Tables
tables : ekko, " Purchase order Header
 ekpo, " Purchase order Item
 marc. " Material with Plant data
Internal table for output.
data : begin of i_output occurs 0,
 ebeln like ekko-ebeln,
 matnr like ekpo-matnr,
 end of i_output.
ALV Data declaration.
data : v_repid like sy-repid.
ALV Function Module Variables
DATA: gs_layout type slis_layout_alv,
 g_exit_caused_by_caller,
 gs_exit_caused_by_user type slis_exit_by_user.
DATA: gt_fieldcat type slis_t_fieldcat_alv,
 gs_print type slis_print_alv,
 gt_events type slis_t_event,
 gt_list_top_of_page type slis_t_listheader,
 g_status_set type slis_formname value 'PF_STATUS_SET',
 g_user_command type slis_formname value 'USER_COMMAND',
 g_top_of_page type slis_formname value 'TOP_OF_PAGE',
 g_top_of_list type slis_formname value 'TOP_OF_LIST',
 g_end_of_list type slis_formname value 'END_OF_LIST',
 g_variant LIKE disvariant,
 g_save(1) TYPE c,
 g_tabname_header TYPE slis_tabname,
 g_tabname_item TYPE slis_tabname,
 g_exit(1) TYPE c,
 gx_variant LIKE disvariant.
data : gr_layout_bck type slis_layout_alv.
Ranges
ranges r_eindt for eket-eindt.
initialization.
v_repid = sy-repid.
start-of-selection.
Get the data from EKKO ,EKPO and MARC Table
perform get_data_tables.
end-of-selection.
display the data in the form of ALV
perform display_data.
*& Form get_data_tables
 Get the data from EKKO,EKPO and MARC Table
FORM get_data_tables.
clear : i_output.
refresh : i_output.
fill the dates in ranges
r_eindt-low = sy-datum - 7.
r_eindt-high = sy-datum + 14.
r_eindt-option = 'BT'.
r_eindt-sign = 'I'.
append r_eindt.
Get the data from EKKO,EKPO and EKET Tables
select aebeln bmatnr into table i_output
 from ekko as a inner join
 ekpo as b on aebeln = bebeln
 inner join marc as c on cmatnr = bmatnr
 inner join mara as d on dmatnr = bmatnr
 inner join eket as e on eebeln = aebeln
 and eebelp = bebelp
 where c~beskz = 'E'
 and c~werks = '1000'
 and d~mtart = 'FERT'
 and b~loekz = space
 and b~elikz = space
 and e~eindt in r_eindt.
if sy-subrc ne 0.
message e000(zwave) with 'No open purchase order found'.
endif.
ENDFORM. " get_data_tables
*& Form display_data
 text
FORM display_data.
Fill the Fiedlcat
PERFORM fieldcat_init using gt_fieldcat[].
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 I_INTERFACE_CHECK = ' '
 I_BYPASSING_BUFFER =
 I_BUFFER_ACTIVE = ' '
 I_CALLBACK_PROGRAM = v_repid
 I_CALLBACK_PF_STATUS_SET = ' '
 I_CALLBACK_USER_COMMAND = g_user_command
 I_CALLBACK_TOP_OF_PAGE = ' '
 I_CALLBACK_HTML_TOP_OF_PAGE = ' '
 I_CALLBACK_HTML_END_OF_LIST = ' '
 I_STRUCTURE_NAME =
 I_BACKGROUND_ID = ' '
 I_GRID_TITLE =
 I_GRID_SETTINGS =
 IS_LAYOUT = gr_layout_bck
 IT_FIELDCAT = gt_fieldcat[]
 IT_EXCLUDING =
 IT_SPECIAL_GROUPS =
 IT_SORT =
 IT_FILTER =
 IS_SEL_HIDE =
 I_DEFAULT = 'X'
 I_SAVE = g_save
 IS_VARIANT =
 IT_EVENTS =
 IT_EVENT_EXIT =
 IS_PRINT =
 IS_REPREP_ID =
 I_SCREEN_START_COLUMN = 0
 I_SCREEN_START_LINE = 0
 I_SCREEN_END_COLUMN = 0
 I_SCREEN_END_LINE = 0
 IT_ALV_GRAPHICS =
 IT_ADD_FIELDCAT =
 IT_HYPERLINK =
 I_HTML_HEIGHT_TOP =
 I_HTML_HEIGHT_END =
 IT_EXCEPT_QINFO =
IMPORTING
 E_EXIT_CAUSED_BY_CALLER =
 ES_EXIT_CAUSED_BY_USER =
 TABLES
 T_OUTTAB = i_output
 EXCEPTIONS
 PROGRAM_ERROR = 1
 OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " display_data
*& Form fieldcat_init
 text
 -->P_GT_FIELDCAT[] text
FORM fieldcat_init USING e01_lt_fieldcat type slis_t_fieldcat_alv.
DATA: LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
Purchase order number
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'EBELN'.
LS_FIELDCAT-ref_fieldname = 'EBELN'.
LS_FIELDCAT-ref_tabname = 'EKKO'.
LS_FIELDCAT-TABNAME = 'I_OUTPUT'.
ls_fieldcat-seltext_L = 'Purchase Order'.
ls_fieldcat-seltext_M = 'Purchase Order'.
ls_fieldcat-seltext_S = 'Purchase Order'.
APPEND LS_FIELDCAT TO E01_LT_FIELDCAT.
Material #
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'MATNR'.
LS_FIELDCAT-ref_fieldname = 'MATNR'.
LS_FIELDCAT-ref_tabname = 'EKPO'.
LS_FIELDCAT-TABNAME = 'I_OUTPUT'.
ls_fieldcat-seltext_L = 'Material'.
ls_fieldcat-seltext_M = 'Material'.
ls_fieldcat-seltext_S = 'Material'.
APPEND LS_FIELDCAT TO E01_LT_FIELDCAT.
ENDFORM. " fieldcat_init

No (suitable) item found for purchase order

Dear All,
The order is stock transfer order (STO) item category U. i saw GR is already create. GI and also DCGR. i want to do DCIR which is invoice receipt in tcode mr01, the error "No (suitable) item found for purchase order" is coming out. What would be the cause of this situation? i check with old last PO it is same set with the one that having in problem. i also double click the item to see the detail and what i can see tick option for del completed and no tick on final del.
no GR-based-4 or invoice receipt option to tick. means no tick option for this. but when i see previous po also same. but there is history on DCIR.
Really need to know what should i do? is bug?
Regards
Aishah

In case of out company it was SA(schudule agrement) PO we try on the Credit memo by MIRO t-code through IV
but we met the same error message
The problem cause of not exist delivery schedule quantiry we have put in the qty to there by manually after than this issue cleared.
Hoil.

No goods receipt possible for purchase order message number# M7036

Hello,
We are working in 4.7C , Created the scheduling agreements, with Shipping notification(Inbound delivery) .
Created the Scheduling agreement on 25.09.2009 and created the schedule line one same day with date 25.09.2009, (time column Blank).
So in Practice for Goods receipt we are using MB0A t code for GR,(not using MIGO)..while MB0A..iam going to make GR with ref to Shipping notification then system will through below given message.
No goods receipt possible for purchase order
5500001447 0001
Message no. M7036
tried every thing but unable get. shar your views
Regards
Sapman man

Hi
If you use Shipping notification then you have to create inbound delivery VL31n and do the PGR in inbound delivery VL32N itself.
Incase of scheduling agreement schedule lines you have to make sure the following
1) Schedule line delivery date shoud be todays date or in the past
2) Schedule must be released by using message type based on the type of schedule ( Normal, JIT or forecast)
Hope it helps
Thanks/Karthik

Activating conditions for Purchase Order workflows in EBP

Dear SRMer's,
I am facing the following problem:
System Info :SRM Server 5.5, ECC 6.0
Scenario 1:
All start conditions for Purchase Order in SAP Business Workflow are activated.
I created a direct procurement shopping cart (DP) in SRM browser and ordered it, then I logged in as proffessional purchaser, changed the Price and processed the DP PO.
When Ordering, the follow on Documents are created, but says the PO is waiting for approval. When I check for this PO in the Backend R/3 system in the Me22n (Display PO changes), I don't see the PO.
Scenario 2:
All Start conditions for Purchase Order in SAP Business Workflow are de-activated
I created another direct procurement shopping cart (DP2) in SRM browser and ordered it, then I logged in as proffessional purchaser, changed the Price and processed the DP2 PO (Status is held).
When Ordering, I get the Warning message, no workflow found, contact system administrator.
Please advice what needs to be configured for the PO to be ordered successfully.
Thanks in advance
Raj

Hi,
In your scenario 1, if system is saying that there the PO has to be approved, it means that you have managed the user that will receive the workitem..
Activating all PO WF is not a solution as in standard there are two many cases activated (amount, role, limit...)
I propose you to first activate only the 0 step WF and to overwrite the code inside
Just code that every PO modification should trigger O step WF thus it will be more simple to test it.
Later on, if you want to implement more complex starting conditions, you just have to modify the WF content...
Kind regards,
Yann

For Purchase order, is any Smartform available

Hi,
for Purhcase order Medruck Script is available but I want a smart form for purchase
is there smart form available for purchase order if exists plz. give me the name.
it is very urgent.
Ganesh

Hi Ganesh,
There is standard smartform for PO (pre-configured forms) but you have to import package :/SMB40
PO Form: /SMB40/MMPO_L
Print Program: /SMB40/FM06P
See the note 595812: it explain how to download the preconfigured smartforms.
Anyway this is an extract of that note:
Detailed information can be accessed at the site:
http://service.sap.com/preconfiguredforms OR
http://service.sap.com/smb/development/preconfiguredforms.
To download preconfigured smartform package, please:
1. Go to http://service.sap.com/installations, select tab "download".
2. On the right hand side screen, locate navigation tree node
SAP Software Distribution Center->Download->Installations and Upgrades->
Entry by Application Group.
3. In the main window (right hand side), follow the path
SAP Best Practices->Best Practices for mySAP All-in-One-> PRECONFIGURED
SMART FORMS, you can find available preconfigured smartform versions.
Here you can also download the PO smartform.
Hope this will help.
Regards,
Ferry Lianto

User Exit for Purchase Order Release Strategy

Hi,
I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
Thanks in advance.
Mick

Hi
Check the following Exits and BADI for Pur Requisition
Enhancement
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MM06E011 Activate PReq Block
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MEETA001 Define schedule line type (backlog, immed. req., preview)
ME590001 Grouping of requsitions for PO split in ME59
M06E0005 Role determination for release of purchasing documents
M06E0004 Changes to communication structure for release purch. doc.
M06B0005 Changes to comm. structure for overall release of requisn.
M06B0004 Number range and document number
Business Add-in
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_PURCHDOC_POSTED Purchasing Document Posted
SMOD_MRFLB001 Control Items for Contract Release Order
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_REQ_POSTED Purchase Requisition Posted
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_BSART_DET Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN Commitment for return item
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CHECK_OA Check BAdI for Contracts
Reward points if useful
Rgds,
Naren

User Exit/BADI for Purchase Order and Purchase Requisitions

HI,
I have a requireent where i have to check the the user does not enter both Subitems and Over a Limit for a Service Purchase Requisition.
Is there a User Exit or Badi that i can use where this information is availaible.
also i have to check that release strategy is assigned to every purchase order where the version has been completed.
Is there a User Exit or Badi where Information of EREV table is availaible.
Regards,
Tarun Bahal

For Purchachase requisition , the BADIs and USER EXITS are
ME_COMMITMNT_PARKING BAdI for Redefining Commitment Interface When Parking
ME_MEREQ_PARKING BAdI Purchase Requisition: "Hold"
ME_REQ_HEADER_TEXT Copy Header Text: Enjoy Purchase Requisition
try with the above BADI's
MEREQ001 Customers' Own Data in Purchase Requisition
for Purchase order , the BADIs and USER EXITS are
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_BAPI_PO_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PR_CREATE_02
ME_BSART_DET Change document type for automatically generated POs
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_CHECK_OA Check BAdI for Contracts
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_COMMITMENT_RETURN Commitment for return item
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PURCHDOC_POSTED Purchasing Document Posted
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_REQ_POSTED Purchase Requisition Posted
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
SMOD_MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting
LMELA010 Inbound shipping notification: Transfer item data from
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Rece
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition rel
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requi
M06E0004 Changes to communication structure for release purch. d
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., previe
MEFLD004 Determine earliest delivery date f. check w. GR (only P
MELAB001 Gen. forecast delivery schedules: Transfer schedule imp
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery toler
MM06E001 User exits for EDI inbound and outbound purchasing docu
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into P
MM06E008 Monitoring of contr. target value in case of release or
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound proces
MMAL0004 ALE purchasing info record distribution: Inbound proces
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001
Regards,
Anirban

Whats the fieldname and table name for purchase order delivery date

hi all,
whats the fieldname and table name for purchase order delivery date
thanks and regrads

EKET-EINDT is the delivery date according to the schedule lines.
for example the line item has 100 qty.
it is sent in three schedules (40, 40, 20).
Then EKET will have 3 records for one PO Line item.
The final delievry data is the EKET-EINDT for the 3rd schedule line item.
Regards,
Ravi

Searching for Workflow for Purchase Order Change

Hi experts!
We are using SRM5.0 / extended classic scenario and backend R/3 4.7 Enterprise.
We should implement an approver process for the purchase order changes. Does any one of you know whether there exists a standard SAP workflow?
Many thanks for your help.
Regards,
Corinne

Hi
Please refer to the following links for detailed step-by-step details.
Workflows for Purchase Orders - n-step approval workflow ( WS14000145 )... Start WS14000075, WS14000089 or WS14000145...-step approval workflow ( WS14000145 )
http://help.sap.com/saphelp_srm50/helpdata/en/5a/c5173f5ff48443e10000000a114084/frameset.htm
Authorization - Purchase orders ( WS14000145 )
http://help.sap.com/saphelp_srm50/helpdata/en/f7/a6a3415e34b05fe10000000a1550b0/frameset.htm
Setting Up SAP Business Workflow - WS14000145 ( n-step approval )... WS14000145... WS14000145 N-step approval PO WS14000145 N-step approval of contract
http://help.sap.com/saphelp_srm50/helpdata/en/2c/e68d406b305537e10000000a1550b0/frameset.htm
Dynamic Modification - Purchase orders ( WS14000145 )
http://help.sap.com/saphelp_srm50/helpdata/en/84/dda441e79ead5fe10000000a1550b0/frameset.htm
Back & Forth Processing and the Retain Function - Purchase orders ( WS14000145 ) 
http://help.sap.com/saphelp_srm50/helpdata/en/6b/eca441eea7ef0be10000000a1550b0/frameset.htm
Approval Workflows for Purchase Orders and Change Versions
http://help.sap.com/saphelp_srm50/helpdata/en/ec/fe163ff8519a06e10000000a114084/frameset.htm
Workflow for Contracts - Workflow for Purchase Orders ( WS14000145 )
http://help.sap.com/saphelp_srm50/helpdata/en/26/0f8b41ed891609e10000000a155106/frameset.htm
SRM Business Workflow - One-step Approval
http://help.sap.com/saphelp_srm50/helpdata/en/8b/4fa9585db211d2b404006094b92d37/frameset.htm
WS14000089
http://help.sap.com/saphelp_srm50/helpdata/en/5a/c5173f5ff48443e10000000a114084/frameset.htm
WS14000075
http://help.sap.com/saphelp_srm50/helpdata/en/2c/e68d406b305537e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/5a/af5efc85d011d2b42d006094b92d37/frameset.htm
Regards
- Atul

Modification in MEDRUCK for purchase order, RFQ, scheduling agreement.....

Similar Messages

Maybe you are looking for