OTL need to require user enter a purchase order number

We are using the Projects and Purchasing timecard layout. OTL validates the PO entered, but I need to require that it be entered. Seems OTL doesn't require it and I can't find anything in preferences.
I can write a validation rule to enforce it, but does anyone know if there's an easier way like telling OTL which fields on the timecard layout are required? Thanks.

Hi Mahesh,
My suggetion is that develope program to do your scenario... Use BAPI to create Sales order. First confirm with the Functional team for the input for sales order about sales area, company code, conditions type to be used while creation a sales order against Purchaser order... If the details is same then. First get the details of the Purchase order from BAPI " 'BAPI_PO_GETDETAIL' or you can get details by select queries on EKKO & EKPO for header and details....
Then pass data to BAPI of sales order creation 'BAPI_PO_CREATE' . to create sales order and handle error with parameter RETURN = IT_BAPIRETURN
by giving loop on that....and display in the output.....
This is the simplest way of doing your process...
If any other help please let me know.....
reward points..
Cheers,
Sagun Desai....

Similar Messages

Need help on smartform to print purchase order.

Hello all,
            I need your help. I am struck in the following problem. In transaction ME23N for displaying purchase order, you enter the
purchase order number and then you click on print preview and print off from the printer icon in the top of the preview. My client
wants me to remove the print button or print icon from the print preview of the purchase order. How can i accomplish this? Iam new to
abap, plz help me out... thanks in advance...
Is there any user exit/ field exit to accomplish this? Or is there any better alternative to this... please let me know at the earliest possible. thanks
Cheers,
Jwelit.

You need to change the driver program of the Smartform to restrict to only Print Preview.
If you are using any standard Output/message type than you need to copy that to your Z output type. Tcode NACE can help you. Than you need to copy the driver program attached to your output type.
Now, in your copied Z program, you need to set some parameter of the Smartform FM.
DATA: LS_COMPOSER_PARAM     TYPE SSFCOMPOP.
LS_COMPOSER_PARAM-TDNOPRINT = 'X'.
Than you need to pass this to your SMARTForm FM.
Like:
    CALL FUNCTION LF_FM_NAME
      EXPORTING
        ARCHIVE_INDEX      = TOA_DARA
        ARCHIVE_PARAMETERS = ARC_PARAMS
        CONTROL_PARAMETERS = LS_CONTROL_PARAM
        MAIL_RECIPIENT     = LS_RECIPIENT
        MAIL_SENDER        = LS_SENDER
        OUTPUT_OPTIONS     = LS_COMPOSER_PARAM   " <<
        ZXEKKO             = L_DOC-XEKKO " user_settings = ' '
        ZXPEKKO            = L_DOC-XPEKKO
Regards,
Naimesh Patel

Defining Purchase Order Number as a Required Entry

Dear All,
I've cut and pasted the contents of sap.help.com below, I'm trying to make the Purchase order Number in sales order document a required entry but I'm unable to locate the checkbox in VD02 as mentioned in help text. can some one help me out.
Defining Purchase Order Number as a Required Entry:
Use:
If a customer order number appears on the order for that customer, you can define the PO number (purchase order number) field as a required entry.
Procedure:
Choose Logistics ® Sales/distribution ® Master data ® Business partners ® Sold-to party ® Change ® Change.
Enter the customer and select the Control data view in the General data area of the screen and choose Enter.
The system now displays the Customer Change: Control Data screen. In the Reference data/area section, select the Purchase order req. checkbox. Save the customer master.
Result:
You will have to enter the purchase order number on the Order Entry screen for this customer in all future orders.

Hi
TRy transaction VOV8
select sales document type and go to general control and select Enter PO number check box.
Otherwise you can create your own incompletion procedure in OVA2 and maintain whatever field you want mandatory and asign this procedure to sales document type with transaction VUA2 and mark IC dialog.
regards
Srinivas

BADI / User exit for Purchase order(ME21N) after saving the document

Hi expert,
I need the BADI / User exit for Purchase order(ME21N) after saving the document
This is for email sending after create the purchase order so PO document number will be the import parameter
pls help me
point will be reward
Regards,
Ganesh

Hi Ganesh,
Could you please share your solution?
Thanks.
Hoops
Edited by: Hoops on Jun 13, 2011 10:51 PM

Goods Receipt Screen: Purchase Order number stored

Hi all.
SRM 4.0, server 5.5.
When going into the Goods Receipt screen (BBPCF02 for example), the field Purchase Order Number is pre-filled with the latest PO, that a user has searched for. How could I make sure, that this screen is not filled out with the latest PO but just let the screen display the open POs from within the timeframe? I have too many users that have made a GR, return to the GR screen and then their previous PO number is stored, and they believe they still have not made the GR for that PO, so they do it again. I need to make sure, that the purchase order number value is never stored in this field - any ideas?

OMBT click on the groups button, select the
Material documents for goods movements and inventory diffs.
WA WE WF WH WI WL WO WQ WR WS WV WW WZ
And then select the maintain icon, you need to maintain the number range
for the year 2010.
ands OMBA for accounting finance doc number range
hope this helps

User Exit for Purchase Order Line Items.

I have been trying to search for a User Exit for Purchase Order Line Items and have been unable to do find anything. I need to overwrite the Net Price and Pricing Condition on a certain type of material based upon the Pricing Condition for that Line Item which is on the Sales Document. Any direction you can point me into would be greatly appreciated. Thanks.

Thanks for pointing me in the right direction. I was able to create my first BADI using the PROCESS_ITEM method. The following link was also very helpful: Re: BADI ME_PROCESS_PO_CUST Method:PROCESS_ITEM

I Need interactive report to list the purchase orders details for a vendor

I Need interactive report to list the purchase orders details for a vendor that has interactive drill down options to give the detail of vendor from vendor master.

Hi
see this sample report
this is Customer wise sales orders
just make similar report just using LFA1, EKKO and EKPO tables instead of KNA1,VBAK,VBAP
REPORT ZTEJ_INTAB1 LINE-SIZE 103 LINE-COUNT 35(5) NO STANDARD PAGE
HEADING.
*TABLES DECLARATION
TABLES : KNA1, VBAK, VBAP.
*SELECT OPTIONS
SELECT-OPTIONS: CUST_NO FOR KNA1-KUNNR.
*INITIALIZATION
INITIALIZATION.
CUST_NO-LOW = '01'.
CUST_NO-HIGH = '5000'.
CUST_NO-SIGN = 'I'.
CUST_NO-OPTION = 'BT'.
APPEND CUST_NO.
*SELECTION SCREEN VALIDATION
AT SELECTION-SCREEN ON CUST_NO.
LOOP AT SCREEN.
IF CUST_NO-LOW < 1 OR CUST_NO-HIGH > 5000.
MESSAGE E001(ZTJ1).
ENDIF.
ENDLOOP.
*BASIC LIST SELECTION
START-OF-SELECTION.
SELECT KUNNR NAME1 ORT01 LAND1 INTO
(KNA1-KUNNR, KNA1-NAME1,KNA1-ORT01,KNA1-LAND1)
FROM KNA1
WHERE KUNNR IN CUST_NO.
WRITE:/1 SY-VLINE,
KNA1-KUNNR UNDER 'CUSTOMER NO.' HOTSPOT ON,
16 SY-VLINE,
KNA1-NAME1 UNDER 'NAME',
61 SY-VLINE,
KNA1-ORT01 UNDER 'CITY',
86 SY-VLINE,
KNA1-LAND1 UNDER 'COUNTRY',
103 SY-VLINE.
HIDE: KNA1-KUNNR.
ENDSELECT.
ULINE.
*SECONDARY LIST ACCESS
AT user-command.
IF SY-UCOMM = 'IONE'.
PERFORM SALES_ORD.
ENDIF.
IF SY-UCOMM = 'ITWO'.
PERFORM ITEM_DET.
ENDIF.
*TOP OF PAGE
TOP-OF-PAGE.
FORMAT COLOR 1.
WRITE : 'CUSTOMER DETAILS'.
FORMAT COLOR 1 OFF.
ULINE.
FORMAT COLOR 3.
WRITE : 1 SY-VLINE,
3 'CUSTOMER NO.',
16 SY-VLINE,
18 'NAME',
61 SY-VLINE,
63 'CITY',
86 SY-VLINE,
88 'COUNTRY',
103 SY-VLINE.
ULINE.
FORMAT COLOR 3 OFF.
*TOP OF PAGE FOR SECONDARY LISTS
TOP-OF-PAGE DURING LINE-SELECTION.
*TOP OF PAGE FOR 1ST SECONDARY LIST
IF SY-UCOMM = 'IONE'.
ULINE.
FORMAT COLOR 1.
WRITE : 'SALES ORDER DETAILS'.
ULINE.
FORMAT COLOR 1 OFF.
FORMAT COLOR 3.
WRITE : 1 SY-VLINE,
3 'CUSTOMER NO.',
16 SY-VLINE,
18 'SALES ORDER NO.',
40 SY-VLINE,
42 'DATE',
60 SY-VLINE,
62 'CREATOR',
85 SY-VLINE,
87 'DOC DATE',
103 SY-VLINE.
ULINE.
ENDIF.
FORMAT COLOR 3 OFF.
*TOP OF PAGE FOR 2ND SECONDARY LIST
IF SY-UCOMM = 'ITWO'.
ULINE.
FORMAT COLOR 1.
WRITE : 'ITEM DETAILS'.
ULINE.
FORMAT COLOR 1 OFF.
FORMAT COLOR 3.
WRITE : 1 SY-VLINE,
3 'SALES ORDER NO.',
40 SY-VLINE,
42 'SALES ITEM NO.',
60 SY-VLINE,
62 'ORDER QUANTITY',
103 SY-VLINE.
ULINE.
ENDIF.
FORMAT COLOR 3 OFF.
*END OF PAGE
END-OF-PAGE.
ULINE.
WRITE :'USER :',SY-UNAME,/,'DATE :', SY-DATUM, 85 'END OF PAGE:',
SY-PAGNO.
SKIP.
*& Form SALES_ORD
*& FIRST SECONDARY LIST FORM
FORM SALES_ORD .
SELECT KUNNR VBELN ERDAT ERNAM AUDAT INTO
(VBAK-KUNNR, VBAK-VBELN, VBAK-ERDAT, VBAK-ERNAM, VBAK-AUDAT)
FROM VBAK
WHERE KUNNR = KNA1-KUNNR.
WRITE:/1 SY-VLINE,
VBAK-KUNNR UNDER 'CUSTOMER NO.' HOTSPOT ON,
16 SY-VLINE,
VBAK-VBELN UNDER 'SALES ORDER NO.' HOTSPOT ON,
40 SY-VLINE,
VBAK-ERDAT UNDER 'DATE',
60 SY-VLINE,
VBAK-ERNAM UNDER 'CREATOR',
85 SY-VLINE,
VBAK-AUDAT UNDER 'DOC DATE',
103 SY-VLINE.
HIDE : VBAK-VBELN.
ENDSELECT.
ULINE.
ENDFORM. " SALES_ORD
*& Form ITEM_DET
*& SECOND SECONDARY LIST FORM
FORM ITEM_DET .
SELECT VBELN POSNR KWMENG INTO
(VBAP-VBELN, VBAP-POSNR, VBAP-KWMENG)
FROM VBAP
WHERE VBELN = VBAK-VBELN.
WRITE : /1 SY-VLINE,
VBAP-VBELN UNDER 'SALES ORDER NO.',
40 SY-VLINE,
VBAP-POSNR UNDER 'SALES ITEM NO.',
60 SY-VLINE,
VBAP-KWMENG UNDER 'ORDER QUANTITY',
103 SY-VLINE.
ENDSELECT.
ULINE.
ENDFORM. " ITEM_DET
REPORT demo_list_at_pf.
START-OF-SELECTION.
WRITE 'Basic List, Press PF5, PF6, PF7, or PF8'.
AT pf5.
PERFORM out.
AT pf6.
PERFORM out.
AT pf7.
PERFORM out.
AT pf8.
PERFORM out.
FORM out.
WRITE: 'Secondary List by PF-Key Selection',
/ 'SY-LSIND =', sy-lsind,
/ 'SY-UCOMM =', sy-ucomm.
ENDFORM.
After executing the program, the system displays the basic list. The user can press the function keys F5 , F6 , F7 , and F8 to create secondary lists. If, for example, the 14th key the user presses is F6 , the output on the displayed secondary list looks as follows:
Secondary List by PF-Key Selection
SY-LSIND = 14
SY-UCOMM = PF06
Example for AT USER-COMMAND.
REPORT demo_list_at_user_command NO STANDARD PAGE HEADING.
START-OF-SELECTION.
WRITE: 'Basic List',
/ 'SY-LSIND:', sy-lsind.
TOP-OF-PAGE.
WRITE 'Top-of-Page'.
ULINE.
TOP-OF-PAGE DURING LINE-SELECTION.
CASE sy-pfkey.
WHEN 'TEST'.
WRITE 'Self-defined GUI for Function Codes'.
ULINE.
ENDCASE.
AT LINE-SELECTION.
SET PF-STATUS 'TEST' EXCLUDING 'PICK'.
PERFORM out.
sy-lsind = sy-lsind - 1.
AT USER-COMMAND.
CASE sy-ucomm.
WHEN 'FC1'.
PERFORM out.
WRITE / 'Button FUN 1 was pressed'.
WHEN 'FC2'.
PERFORM out.
WRITE / 'Button FUN 2 was pressed'.
WHEN 'FC3'.
PERFORM out.
WRITE / 'Button FUN 3 was pressed'.
WHEN 'FC4'.
PERFORM out.
WRITE / 'Button FUN 4 was pressed'.
WHEN 'FC5'.
PERFORM out.
WRITE / 'Button FUN 5 was pressed'.
ENDCASE.
sy-lsind = sy-lsind - 1.
FORM out.
WRITE: 'Secondary List',
/ 'SY-LSIND:', sy-lsind,
/ 'SY-PFKEY:', sy-pfkey.
ENDFORM.
When you run the program, the system displays the following basic list with a the page header defined in the program:
You can trigger the AT LINE-SELECTION event by double-clicking a line. The system sets the status TEST and deactivates the function code PICK. The status TEST contains function codes FC1 to FC5. These are assigned to pushbuttons in the application toolbar. The page header of the detail list depends on the status.
Here, double-clicking a line no longer triggers an event. However, there is now an application toolbar containing five user-defined pushbuttons. You can use these to trigger the AT USER-COMMAND event. The CASE statement contains a different reaction for each pushbutton.
For each interactive event, the system decreases the SY-LSIND system field by one, thus canceling out the automatic increase. All detail lists now have the same level as the basic list and thus overwrite it. While the detail list is being created, SY-LSIND still has the value 1.
Regards
Anji

Inspection Type 05 require input purchase order number for rejection

Hi Experts,
I have inspection and needed to reject in QA12.
When inputting the stock posting quantity to return, it prompts the reason for rejection, and required to input purchase order number also.
Since that is material return from production(inspection type 05) with no purchase order number, where in SPRO I can check the setting of this and disable this?
Please kindly advise, thanks!
Regards,
Daniel

Hi SujitSND,
I have some materials in inspection lot which is created from material return in production.
This lot is rejected by QA and needed to return to production line.
When inputting the qualtity field RETURN DELIVERY, system forced me to input Purchase Order number which is not available.
My target is to not needing to input purchase order.
Regards,
Daniel

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

Need of Tables names that link Purchase Order and the Confirmation Number

Hi All,
Can any one help me please regarding EBP tables. I am new to EBP so not aware of data flow in the EBP data dictionary.
Please can anyone explain the tables which link the Purchase order number and the Confirmation(Goods Receipt).
Please do the needful.
Thanks in advance.

Hi,
You can query the tables BBP_PDHGP and BBP_PDIGP to get teh refernce doc no for PO and then use FM BBP_PD_CONF_GETDETAIL to get the details fo a particular confirmation.ALso you can search confirmations by "Reference Document", use BBP_PD_CONF_GETLIST, with parameter I_REF_DOC_NO, and then use BBP_PD_CONF_GETDETAIL for the found confirmations.
HTH.
BR,
Disha.
PLs reward points for helpful answers

I need a purchase order number immediately option in I-proc

Hello,
I created one catalog requisition in I-Proc, and checked " I need a purchase order number immediately" option during checkout. This requisition has been created and i even got message that "Purchase order number 45 has been reversed for you" With this being said...
1. Where can i see this PO number ( I approved above requisition, but i can not see this PO number in PO screen)...?
2. What does this purchase order number do?
Thanks
Deepak

Hi Depak,
Please check this doc...
PO Create Documents
Workflow File Name: poxwfatc.wft
This workflow manages the automatic creation of purchasing documents. The PO Create Documents workflow starts in Oracle iProcurement when you submit a
requisition associated with an existing blanket purchase agreement, contract purchase agreement, or catalog quotation in Oracle Purchasing. Customize the attributes in this workflow to fit your business needs.
The following table shows the attributes that you must consider:
1) Is Automatic Creation Allowed?
Please change to Y
AUTOCREATE_DOC Indicator (Y for Yes or N for No) of whether this workflow is initiated for all approved requisition lines.
Default value: N
2) Is Automatic Approval Allowed?
AUTO_APPROVE_DOC Indicator of whether the purchase order approval workflow is initiated automatically after this workflow.
Default value: N
Please change to Y
3) Should Workflow Create The Release?
CONT_WF_FOR_AC_REL_GEN Indicator of whether this workflow creates, releases, or leaves them to the buyer to create using AutoCreate in Oracle Purchasing.
Default value: N
Please change to Y
You can verify the changes through below query..
select rtrim(w.name) name,
w.text_default Value,
rtrim(w.item_type) item_type
from wf_item_attributes w
where w.NAME in ('AUTO_APPROVE_DOC', 'CONT_WF_FOR_AC_REL_GEN', 'AUTOCREATE_DOC')
Hope this will help.
Regards,
S.P DASH
Another quick question to you, you mentioned UNSPENT code in your queries.. I think it should be UNSPSC code...correct me if I am wrong here..

User Exit for Purchase Requisition Number Range

Dear Experts,
I searched on sdn, i got M06B0003 &M06B0004 this 2 user exit for PR Number range.
I have activated both User exits but while creating PR is not getting effect of that user exit.
I have checked by putting Break-point in respective user exit but while saving the PR it should go to that break-point but it not going there aslo.
And also i have checked user exit MM06E003 but it is for Purchase Order number range.And for PO it is working.
Please help me to solve this issue.Solution will be appreciated.
Regards,
Sanket.

Hi,
Sorry that badi will not help try this one ...EXIT_SAPLMEREQ_009 in MEREQ001 where the export parameters is purchase requisition number....
Thanks,
Shailaja Ainala.

Purchase order number ranges plant wise

Hi ,
Requirement is , want to have purchase order number plant wise. I know that we can have different number ranges for different document types in standard SAP. But how to achieve different number ranges for purchase order plant wise.?
Is there any user exits available for this?
regards,
abi

Hi,
it is possible through a BADI to get the separate number ranges for plant wise PR/PO,
but u need to maintain a customised table with number ranges and plants,
whenever the user try to save a PO/PR the syatem will pick the number range from the customised table,
that BADI is ME_PROCESS_PO_CUST,
it is very useful if any client has number of plants like 30 or 40 plants,
and it is easy track the PO from where it has raised.
rgds

AS01 - Purchase order number in asset

Hello dear all,
User wants to add manually the purchase order number of asset in the asset master record.
This field doesn't exist in the standard.
What is the best solution for this request ?
Thank you in advance ?

Hello,
This requirement is not logical, as you might have several POs assigned to one asset. However, the user can use any free field in the asset master data to enter this information, if he would like to. There iseven a possibility to add user-defined field to the master record, if required.
Regards,
Eli

Copy purchase order number and date from one sales order to other sales ord

Hi,
I am creating sales order in va01. here i am entering purchase order number (p100) and date. Sales order number ex: 42000
I am creating another sales order with reference to 42000. when creating sales order with reference to 42000, purchase order number (p100) and date has to be copied automatically from that order.
Can anyone please give me a solution?
Thanks in advance
Babu

Dear Babu,
Currently, PO number is being mentioned in copy routine 101 but this
field VBKD-BSTKD is being cleared out.
If we check this routine code:
FORM DATEN_KOPIEREN_101.
Data which is not copied
Pricing date for consignment issue by external service agent from
the scheduling agreement
IF CVBAK-VBTYP CA VBTYP_LP_EDL.
    CLEAR VBKD-PRSDT.
ENDIF.
PO data should not be copied
CLEAR: VBKD-BSTKD,                    <<<<<
         VBKD-BSTDK,
In order to achieve your requirement, you need to consider creating you
own copying routines for VBKD fields copying standard copying routines
(for example copying routine 101) according your business requirements
and change them via transaction VOFM, in order to:
- deactivate the LOCAL: statement
- delete the clear statements
Once you have created those two routines to match your business needs,
you can insert them in transaction VTAA, so the sales order will copy
the PO date at item level.
I hope I was able to help you.
Kind regards,
Zsuzsanna

OTL need to require user enter a purchase order number

Similar Messages

Maybe you are looking for