Lot size calculation for Purchase order

Hi all,
I want to purchase Labels which comes in lot qty such as in lot of 100,200 etc.
For that particular items i want to do mandatory qty lot size in PO when buyers places the purchase order.
Can anybody tell me How i can map that lot size for the particular item.
Regards,
Anant

Hi,
You can done it with change Material Master.
Enter MM02 t-code, enter your material code and select MRP1 view.
Here maintain Rounding value as 100 in material master.
After when your create purchase order system put quantity as 100, 200, 300 etc.
Regards,
Mahesh R.

Similar Messages

Rounding value for purchase order quantity

Hi Guru ,
i need help for logic LOT SIZE MRP.
In particolar i need of use the parameters of rounding for create the planned order multiple of the value.
Example for a requirement of 3800 pz whit a value rounding of 500 i vould want that the system create a planned order of the 4000pz.
I have tried insert this value 500 in the field "Rounding value for purchase order quantity" in the view MRP1 but after run MRP the system create a planned order of the same quantity of the requirement.
Thanks a lot for help
Daniele
PP TEAM

Dear,
OMI4, for lot size select Lot for lot order qty with rounding.
Either you can use the Rounding Value or you can use a Rounding profile in MRP2 view to round of your order qty and rouding value in MRP1 view.
Further you can check
Check FM MD_ROUNDING_VALUE
Regards,
R.Brahmankar

PO 'No goods receipt possible for purchase order'

Hi gurus!
While trying to make Confirmation of a PO in the SRM Portal the user is getting the error 'No goods receipt possible for purchase order'
The scenario used is Classic, so PO is replicated directly to the R/3 system.
Any idea why this is happening?
Thanks a lot!

Hi, thanks for the quick reply!
Where i can check the Item category?
I found a field called 'subitem category' but it's blank
with this possible values:
1 Variant
2 Discount in kind: inclusive bonus qty.
3 Empties
4 Discount in kind: exclusive bonus qty.
5 Prepack item
6 Display item
7 Set item
8 Interchangeable items (IBU: A&D)
9 Pre-packing (SLS items)
H GT Bill of Material, Header Relevant
I GT Bill of Material, Item Relevant
About PO type i think it's EC (doc_type?), in R/3 is shown as EBP PO
I checked in backend system, in the item details > Delivery and the 'Goods Receipt' is checked.

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

Pricing Procedure for Purchase Order

I have to pick item level conditions for value : bed , hr edu cess, edu cess, cst,lst.
I am trying to the pick up fields kbetr and kwert for following conditions from konv table but there are only header level conditons.
so How can i Proceed for this?
For Purchase order script i have used standard Program SAPFM06P.But this a subroutine Pool Program.

hi
Write a Sub-routine in the form, where u can call all the pricing procedures.
write this in the form
/:           PERFORM TAX_AMT IN PROGRAM ZMM_REP_POTAX
/:           USING &EKPO-NETWR& .
/:           CHANGING *xxx-xxx&
write a sub-routine in abap editor , calling the program name and calculating pricing procedures
regards
sailendra kolakaluri

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 message for Purchase Order

Hello,
I've implemented a specific type of message (ZNEU) for purchase order.
With some specifics conditions (not managed in SPRO), I'd like that the ouput message of a purchase order is either the standard one NEU or my specific ZNEU..but noth both as actually.
Is there any user-exit where I can code and change the ouput message determination ?
Thanks a lot in advance.
Best regards
Fanny PONEL ( GROUX).

No user exit for this but this can be control by MN04.
Here you can control the ouyput type trigger
youmay need to configure the access seq and maintian that for your ZNEU conditon.

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

How to find print preview for purchase order like what we find in va03

hi guru's
how to find print preview for purchase order like what we find in va03
let me share ur information
thank u

Hi
You can see the Print Preview/printout etc using the Transaction ME9F for Purchase Order
Execute the ME9F tcode and execute you will get lot of PO's select any Po and press display message
you will see the print preview
Similarly for RFQ output use the Tcode ME9A
for Contrat use ME9K
for GR output use MB90
Reward points for useful Answers
Regards
Anji

SMART FORM FOR PURCHASE ORDER

Hii Experts,
I am developing a smart form for purchase order. I am customizing the existing PO smart form according to the clients requirements. The customer needs fields Discount percentage, Excise duty and VAT/CST%... all these fields when i explored in transaction me23n come from a structure so the values come only at run time.. can anyone tell me the exact table and fields from where these comes so that i can retrieve it from there and display it in my smart form. The fields i need are discount percentage, excise duty and VAT/CST%. its urgent.

REPORT ZMR_PURCHASE_ORDER.
types: BEGIN OF ty_lfa1,
          LIFNR TYPE lfa1-LIFNR,
          MCOD1 TYPE lfa1-MCOD1,
          STRAS TYPE lfa1-STRAS,
          MCOD3 TYPE lfa1-mcod3,
      END OF ty_lfa1.
TYPES: BEGIN OF ty_ekpo,
          ebeln TYPE ekpo-ebeln,
          ebelp TYPE ekpo-ebelp,
          txz01 TYPE ekpo-txz01,
          menge TYPE ekpo-menge,
          peinh TYPE ekpo-peinh,
          brtwr TYPE ekpo-brtwr,
      END OF ty_ekpo.
TYPES: BEGIN OF ty_ekko,
        ebeln TYPE ekko-ebeln, "purchase doc
        LIFNR TYPE ekko-LIFNR, "vendor
        MCOD1 TYPE lfa1-MCOD1, "vendor name
        STRAS TYPE lfa1-STRAS, "vendor add
        MCOD3 TYPE lfa1-MCOD3, "vendor city
        bedat TYPE ekko-bedat, "doc date
        unsez TYPE ekko-unsez, "contact person
        verkf TYPE ekko-verkf, "attn
        telf1 TYPE ekko-telf1, "tele
        ihrez TYPE ekko-ihrez, "ref
        KNUMV TYPE ekko-KNUMV, "doc condition
       ebelp TYPE ekpo-ebelp, "item
       txz01 TYPE ekpo-txz01, "message desc
       menge TYPE ekpo-menge, "qty
       peinh TYPE ekpo-peinh, "rate
       brtwr TYPE ekpo-brtwr, "gross
    END OF ty_ekko.
TYPES: BEGIN OF ty_t685t,
        kschl TYPE t685t-KSCHL,
        vtext TYPE t685t-vtext,
      END OF ty_t685t.
TYPES: BEGIN OF ty_line_item,
        KNUMV TYPE konv-KNUMV, "condition number
        STUNR TYPE konv-STUNR, "step
        kposn TYPE konv-kposn, "item
        KSCHL TYPE konv-KSCHL, "condition type
        vtext TYPE t685t-vtext, "condition name
        KAWRT TYPE konv-KAWRT, "base amt
        KRECH TYPE konv-KSCHL, "calculation type
        qty(13) TYPE n,         "qty
        kbetr TYPE konv-kbetr, "condition rate
        kwert TYPE konv-kwert, "condition value
    END OF ty_line_item.
data: wa_ekko TYPE zms_ekko,
      wa_item TYPE zms_konv,
      wa_lfa1 TYPE ty_lfa1,
      wa_t685t TYPE ty_t685t,
      wa_ekpo TYPE ty_ekpo.
data: it_ekko TYPE TABLE OF zms_ekko,
      it_item TYPE TABLE OF zms_konv,
      it_lfa1 type TABLE OF ty_lfa1,
      it_t685t TYPE TABLE OF ty_t685t,
      it_ekpo TYPE TABLE OF ty_ekpo.
SELECTION-SCREEN : BEGIN OF BLOCK ss_block WITH FRAME TITLE text-001.
   PARAMETERS: pa_ver(2) TYPE c DEFAULT '0'.
    SELECT-OPTIONS: pa_pord FOR wa_ekko-ebeln,
                    pa_date for wa_ekko-bedat.
SELECTION-SCREEN : END OF BLOCK ss_block.
SELECT EBELN LIFNR bedat unsez verkf telf1 ihrez knumv from ekko
    into CORRESPONDING FIELDS OF TABLE it_ekko.
if pa_pord is not INITIAL.
    DELETE it_ekko WHERE ebeln not in pa_pord.
endif.
if pa_date is not INITIAL.
    DELETE it_ekko WHERE bedat not IN pa_date.
endif.
if it_ekko is not INITIAL.
SELECT lifnr MCOD1 STRAS MCOD3 from lfa1
    INTO CORRESPONDING FIELDS OF TABLE it_lfa1
    FOR ALL ENTRIES IN it_ekko
    WHERE LIFNR = it_ekko-LIFNR.
SELECT ebeln ebelp txz01 menge peinh brtwr from ekpo
    INTO CORRESPONDING FIELDS OF TABLE it_ekpo
    FOR ALL ENTRIES IN it_ekko
    WHERE EBELN = it_ekko-ebeln.
loop at it_ekko into wa_ekko.
    READ TABLE it_lfa1 into wa_lfa1 WITH KEY lifnr = wa_ekko-LIFNR.
    wa_ekko-MCOD1 = wa_lfa1-MCOD1.
    wa_ekko-stras = wa_lfa1-stras.
    wa_ekko-MCOD3 = wa_lfa1-MCOD3.
    MODIFY it_ekko FROM wa_ekko TRANSPORTING MCOD1 STRAS MCOD3 WHERE ebeln = wa_ekko-ebeln.
ENDLOOP.
SELECT KNUMV STUNR KPOSN KSCHL KRECH kbetr kwert KAWRT from konv
    into CORRESPONDING FIELDS OF TABLE it_item
    FOR ALL ENTRIES IN it_ekko
    WHERE KNUMV = it_ekko-KNUMV.
SELECT kschl vtext from t685t
    INTO CORRESPONDING FIELDS OF TABLE it_t685t
    FOR ALL ENTRIES IN it_item
    WHERE spras = 'EN' and KSCHL = it_item-KSCHL.
LOOP AT it_item into wa_item.
    READ TABLE it_t685t into wa_t685t with key KSCHL = wa_item-KSCHL.
    wa_item-vtext = wa_t685t-vtext.
    if wa_item-kschl = 'ZBP1'.
      wa_item-qty = wa_item-KAWRT / wa_item-kbetr.
    endif.
    if wa_item-KRECH = 'A'.
     wa_item-kbetr = wa_item-kbetr / 10.
    endif.
    if wa_item-kschl = 'NAVS'.
      wa_item-vtext = 'Sales Tax'.
    endif.
    MODIFY it_item from wa_item TRANSPORTING vtext kbetr kschl qty
      WHERE stunr = wa_item-STUNR and
            kposn = wa_item-kposn.
ENDLOOP.
DELETE it_item WHERE kposn = '000000'.
DELETE it_item WHERE kschl <> 'ZBP1' and kschl <> 'ZD01' and kschl <> 'ZE01'
      and kschl <> 'NAVS' and kschl <> 'ZSRV'.
sort it_item by kposn STUNR.
CALL FUNCTION '/1BCDWB/SF00000025'
EXPORTING
    ARCHIVE_INDEX              =
    ARCHIVE_INDEX_TAB          =
    ARCHIVE_PARAMETERS         =
    CONTROL_PARAMETERS         =
    MAIL_APPL_OBJ              =
    MAIL_RECIPIENT             =
    MAIL_SENDER                =
    OUTPUT_OPTIONS             =
    USER_SETTINGS              = 'X'
IMPORTING
    DOCUMENT_OUTPUT_INFO       =
    JOB_OUTPUT_INFO            =
    JOB_OUTPUT_OPTIONS         =
    TABLES
      it_ekko                    = it_ekko
      it_item                    = it_item
EXCEPTIONS
    FORMATTING_ERROR           = 1
    INTERNAL_ERROR             = 2
    SEND_ERROR                 = 3
    USER_CANCELED              = 4
    OTHERS                     = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endif.

Liquidated Damages calculation in Purchase Order

How to capture the Liquidated Damages calculation in Purchase Order in SAP MM module?
I have seen many posting with the answer that this is not standard process.
But this is very important process in Purchasing and Liquidated Damages is very important process, if in SAP standard system it is not available then how we can cater this required.
Regards

Lets assume delivery date is 1 May and the vendor delays the shipment by 10
days, the GR takes place on 11 May. So the vendor has to pay liquidated
damages for 10 days. We can agree in beginning with the vendor how much
liquidated damages will be charged per day.
So now we can create two new fields in PO. One with Liquidated damages
charges/day and one with total liquidated damages. In this field, it should
look for the days difference between the GR date and delivery date in our
case 10 days * Rs.1000/day = Rs.10,000. This formula needs to be inputted in
the total liquidated damages.
Now we can directly get it posted to IR or if we want it to hit the
material cost, we need to add new condition type to calculation schema and
apply this cost to the condition type by ammending the PO.
Hope I am helpfull.

SAP Rules / Considerations behind ATP for Purchase Orders

Hi
Can anyone guide me to the considerations taken into account for ATP check for Purchase orders,
Kind Regards
Bhavana

Hi,
Please find the logic.
ATP quantity
Specifies the available quantity from each receipt that can still be used to cover further requirements.
Use
The ATP quantity is calculated as follows:
Initially, the ATP quantity of a new receipt is the complete receipt quantity. During the availability check according to ATP logic, the system only takes into account receipts that lie before a requirement. A requirement first reduces the most recent receipt (and thus the ATP quantity of this receipt). If a rest quantity remains for this receipt, this quantity is the new ATP quantity for this receipt and it can be used to cover a further requirement.
If one receipt does not completely cover the requirement, the system reduces further receipts and their ATP quantities until the requirement has been completely covered.
If no further ATP quantity is available to cover a requirement or if a requirement can only be partially covered, then this shortage quantity is displayed in the requirements line as a negative ATP quantity.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/c1/3764f4449a11d188fe0000e8322f96/content.htm
http://help.sap.com/erp2005_ehp_04/helpdata/EN/4c/227d1046e611d189470000e829fbbd/content.htm
and the above links will provide you some idea.
Regards

Sample size calculation for Source Inspection

Dear Gurus,
I have an issue regaring sample size calculation for Source Inspection.
I created a PO for 500 nos.
The sampling procedure assigned in the Quality Plan is %age based (10%).
When Inspection lot is created, system is caluating the Sample size as 500 and not 50.
Moreover, when I go to Result Recording, the Inspection qty for the MIC is shown as 1. If the system is calculating sample size as 500, then the inspection qty for the MIC should also be 500. Moreover, the sample size should be 50 only.
Please provide your inputs on this.
Regards,
Nitin

Thanks Sujit!
Your are correct. It works in the same way as u told.
Assigned you the points for the answer.
Closing the thread.
Regards,
Nitin

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

Table for purchase order status

Hello friends,
There's a tab STATUS in purchase order (tcoe ME21N).
I can't find a table which contains theses statuses.
Anybody knows what's the table for purchase orders status ??
Regards,
Bahia

Hi
PO status is stored in Structure not in the table.
Please use the List displays to get the information like ME2N,ME2L, ME2M, ME2K etc
You can also get the information from the table EKKO, EKPO, EKET,EKBE
Hope it helps
thanks/karthik

Lot size calculation for Purchase order

Similar Messages

Maybe you are looking for