Purchase documents per user

Hi Experts,
Is there any transaction or table where in we can get the purchase documents created by a given user?
Thanks in advance

Dear,
ME23n>Document overview>Selection variant>PO>Dynamicselection>Purchasing document header>Createdby
Reward if helpful
Regards
venu gopal

Similar Messages

Purchasing document per tracking number

hi gurus
Please give me the T-code for the PO no with tracking NO

Hi,
Use <b>MELB</b> -- transaccction code-purchasing documents per req.tracking number

Tcode to list open POs like me2l (Purchasing Documents per Vendor)

Hello,
Is there any transaction code to list Open PO by vendor with the following columns ? me2l looks good, but I don't know how to show the column Schedule Line.
    - Purchasing Document,
    - Item
    - Schedule Line
    - Schedule Quantity
    - Good Received Quantity
    - Open Quantity
In me2l, is still to be delivered column is the same as Open Quantity ?
Thanks,
Andre

in which release are you?
Are you having ALV layout in ME2L or just the old fashioned SAP report layout ?
In ALV layout, you have to click the calendar icon to get to the schedule line, and in my system the scheduline line id is just visible in the first column

Report : ME2J (Purchase document per project)

Hi,
Any one so kind check & reply my following quary.
My client is using SAP 4.7 E . Output of ME2J report with scope of list 'BEST_ALV' is not appear in row and column(excel) formate. Output appear same for 'BEST_ALV' & 'BEST'. However in ME2K report, the output apper in different formate for scope of list 'BEST_ALV' & 'BEST'. Output in ME2N with BEST_ALV appear in row & column formate(excel formate).
Can any one check in your system & tell, whether same problem in your system?
If that, any OSS note is available for it?
Regd,
sp sahu

Hello,
You can save output of that report to excel
system>list>save>local file>spreadsheet> and provide path
BR
Diwakar
reward if useful

Report for finding G/L account per purchasing document / reservation

Is there a report to get a list of G/L account for Purchasing documents / Reservations? If not, can a new scope of list for any standard report such as ME2N / ME2B be created to include the G/L account list?

Hi,
As division is not header field of invoice it is not available in accounting document header as well. Thus it will not be available in any standard reports showning items per account. I'm affraid you need to develop your own report or try to extend existing using user-/customer-exits.
You can find more information in OSS note 13131.
Regards,
Marcin

User exit MM06E005 - Customer fields in purchasing document

Hi,
I am using user exit MM06E005 - Customer fields in purchasing document to validate the line items in PO and display the value at header level.
My requirement is when the user enters the line items and press enter the validated value should get populated at header level.I had included a tab (customer tab) in that the value should get displayed.
likewise for each and every line items the value should keep on changing.
And
I the field that i had added at header shows the value during the save but once we come out and enter again,it is not displaying the same.
Regards
Manoj

Hi,
Indeed the exit which you have specified MM06E005 comprises the enhancement for customizing fields and screens associated with it. may be you might not have activated the screen associated with the exit. the screen might have been created but missed while activating.
Regards,
Jagath

Standard report for history per purchasing document

hello!
Is there any standard report for history per purchasing document that displays also the delivery costs?
Thank you!

Dear Landra,
I think this type of report is not available in SAP, may be you have to write program with ABAPer
I have small idea,try ME2N,ME2k throgh dynamic selection,if available its good
Hope this may helps you
Prem.

User exits when posting purchase document and goods movement (GR)

I want to update some custom tables when posting PO and goods movement (GR) .
Please suggest user exits for both posting.

Check the below exists
FOR PO
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
M06B0004            Number range and document number
M06B0005            Changes to comm. structure for overall release of requisn.
M06E0004            Changes to communication structure for release purch. doc.
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., preview)
MEFLD004            Determine earliest delivery date f. check w. GR (only PO)
MELAB001            Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1            Enhancement to Document Overview ME21N/ME51N
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
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
For Goods Movement
LMR1M001            User exits in Logistics Invoice Verification
LMR1M002            Account grouping for GR/IR account maintenance
LMR1M003            Number assignment in Logistics Invoice Verification
LMR1M004            Logistics Invoice Verification: item text for follow-on docs
LMR1M005            Logistics Inv. Verification: Release Parked Doc. for Posting
LMR1M006            Logistics Invoice Verification: Process XML Invoice
MRMH0001            Logistics Invoice Verification: ERS procedure
MRMH0002            Logistics Invoice Verification: EDI inbound
MRMH0003            Logistics Invoice Verification: Revaluation/RAP
MRMN0001            Message output and creation: Logistics Invoice Verification

Purchasing document flow.

Hello friends,
Could anyone plz tell me the link & the document flow between RFQ, purchase requisition, outline agreement, contract, quotation, scheduling agreement, PIR, puchase order?
When Source determination is carried out, what is the priority in which the source is determined?
Thanks,
Cmehra.

Dear C Mehra,
PR >Release the PR>RFQ>Quotation>Quotation Comparison>PO>Release the PO>GR>Invoice Verification
MM Process flow:
Process Flow
The typical procurement cycle for a service or material consists of the following phases:
1. Determination of Requirements
Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.
2. Source Determination
The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.
3. Vendor Selection and Comparison of Quotations
The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.
4. Purchase Order Processing
The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.
5. Purchase Order Follow-Up
The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.
6. Goods Receiving and Inventory Management
Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and underdeliveries of ordered goods.
7. Invoice Verification
The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.
Pur info record is nothing but a master data like thing which will be maintained for different materials to determine the prices etc.It Specifies the number that uniquely identifies a record.
For Example: an info record is based on Plant Vendor and Material
Based on these three the Material Prices will be calculated
for different combinations different values are taken into consideration.
During pricing it brings these values automatically based on this info record.
Use ME11 Tcode to create this record.
Common Tables used by SAP MM
Below are few important Common Tables used in Materials Management Modules:
EINA Purchasing Info Record- General Data
EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link
MBEW Material Valuation
MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
MOFF Lists what views have not been created
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types
Tcodes:
InfoRecord - ME11
Source List - ME01
RFQ to Vendor - ME41
Sheduling Agreement - ME31L
Contract - ME31K
Raising Quotation - ME47
Comparison of Price - ME49
Creation of PO - ME21N
Goods Receipt - MIGO
Invoice (Bill PAssing) - MIRO
Goods Issue - MB1A
Physical Inventory - MI01( Create doc)
MI04 (Enter Count)
MI07 (Post)
Visit the following thread:
New to Materials Management / Warehouse Management?
http://www.sapgenie.com/abap/tables_mm.htm
http://www.sap-img.com/sap-download/sap-tables.zip
http://www.allsaplinks.com/material_management.html
http://www.training-classes.com/course_hierarchy/courses/2614_SAP_R_3_MM_Invoice_Verification_-_Rel_4_x.php
http://www.sapfriends.com/sapstuff.html
check this out
MM flow
MM flow
MM flow
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSMAT/PSMAT.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARCMM/CAARCMM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_MM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOMDMM/LOMDMM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMMM/BCBMTWFMMM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMIVMVAL/MMIVMVAL.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMWMLVS/MMWMLVS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMISVE/MMISVE.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSMAT/PSMAT.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARCMM/CAARCMM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_MM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_MM.pdf
http://www.sap-basis-abap.com/mm/sap-mm-certification-samples.htm
http://www.sap-img.com/mm015.htm
http://sap.ittoolbox.com/documents/popular-q-and-a/sap-mm-interview-questions-3586
Regards,
Naveen.

Maintain plant wise purchase document type

Hi,
I want to know that is there any way where I can able to maintain plant wise purchase document type.
Thanks.

Please make the following settings
Scenario:
Plant 0001 Should create only PO type NB and PR type NB
Plant 0002 Should create only PO type ZNB and PR type ZNB
TCode : OLME
Create new PR type by copying NB (all dependencies): ZNB <<<Separate number range can be used
Create new PO type by copying NB (all dependencies) : ZNB <<< Separate number range can be used
To avoid accidental assignment of (by users)
Remove linkage of NB PO type to ZNB PR type
Remove linkage of ZNB PO type to NB PR type
TCode: OMDT
Assign PR type per plant per MRP Group for MRP generated PR's
Once MRP is run for materials PRs are created as follows plant 0001 type NB and plant 0002 type ZNB, when they run ME57 to create POs from PRs, ZNB PO type will default to PR types ZNB and NB type to NB.
Authorization objects to be changed for each plant respectively (go to SU21 to look up)
Users of Plant 0001 can only create NB type PR and NB type PO
Purchase Order:
M_BEST_BSA   ACTVT=01; BSART=NB;
Purchase Requisition:
M_BANF_BSA   ACTVT=01;BSART= NB;
M_BANF_WRK ACTVT=01;WERKS= 0001 ;
Users of Plant 0002 can only create ZNB type PR and ZNB type PO
Purchase Order:
M_BEST_BSA   ACTVT=01; BSART=ZNB;
Purchase Requisition:
M_BANF_BSA   ACTVT=01;BSART= ZNB;
M_BANF_WRK ACTVT=01;WERKS= 0002 ;
Ofcourse you need to create output message config for each PO type.
Edited by: Jeevan Sagar on Feb 13, 2012 11:16 PM

MM06E005 - Customer fields in purchasing document

Hi,
I am using user exit MM06E005 - Customer fields in purchasing document to validate the line items in PO and display the value at header level.
My requirement is when the user enters the line items and press enter the validated value should get populated at header level.I had included a tab (customer tab) in that the value should get displayed.
likewise for each and every line items the value should keep on changing.
And
I the field that i had added at header shows the value during the save but once we come out and enter again,it is not displaying the same.
Regards
Manoj

got my solution...

No value in Purchasing Document field in FBL1N Transaction

Hi All,
While executing a report RFITEMAP (Transaction FBL1N), Purchasing Document field is blank while I can see the corresponding Purchasing Document in BSEG table. I have a requirement to show the same in the output. Do we have some settings or ABAP code changes to achieve it?
Any kind of input would be helpful to me.
Rgds,
Khanshi

Hi,
Please read note 152335
You can achieve it via OSS note 112312, but you need to program the BTE as per your business requirements, as stated in the note there is no standard functionality for this.
You may refer to the following wiki page, it has an example, but in the example, another field was used, maybe it can be useful for you.
http://wiki.sdn.sap.com/wiki/x/fg3cCw
regards
Waman

Error while creating purchasing documents

Hi,
Iam a new user to Material Management unable to create any Purchasing docments (PR,RFQ,P.o..etc).
As Iam trying to procure a material for stock, selected the Accountassignment as Unknown.
got following two errors
1.Unknown account assignment not defined for use here
2.Source not included in list despite sorce list requirement
pls suggest me something to avoid these errors and create P.Os.
Thanks

Hi,
I got some clue ,
1. As I have specified it is a stock material, It should not ask for any account assignment.
It is asking because I have not updated the material quantity,value updations in IMG settings for the material type
2.The issue was I have checked the source list for plant in the sorce list configuration settings (SPRO> Materials management>Purchasing>Sourcelist>Define source list requirement at plant level)
And I have not maintained the source list.
If you check the above setting, you need to maintain source list for the material
As you specified I have checked the configuration for combination item category-account assignment for item category that was used when creating purchasing document.
for standard itemcategory,unknown account assignment type has been defined.
Now I could able to create P.Os for stock material by updating qty,value updation in material type, and if I don't update this, and use account assingment as unknown I'm getting the saemerror as "unknown account assignment not defind for use here"
pls let me know how to avoid this error, hep me what are the required settings for making a P.O for accountassignment categories
Thanks

PR Mandatory in creation of Purchasing Document

Hi All,
I need your help in order to create purchasing document is mandatory with PR reference . I have done in config "Define Function Authorizations for Buyers" for all Purchasing Document such as PO, Contract and RFQ then assign them in SU01 for parameter EFB, however, only PO works others do not affect. Is there any parameters besides EFB shold be set in parameter? Thanks.
Best regards,
Mahnansa

Hi,
GOTO Authorization Buyer... tcode OMET(Function Authorization)
then New entry
give any name say 11 & PO from PR only
then at the top in General parameters,in that fiels selection choose----->
NBF
then in possible reference objects----> Choose Ref to PR
save
then
T code SU3, or system-> user profile-> Own data
click parameter
in parameter ID, give EFb, then
In parameter value give 11,just wat u save in OMET,
save.
Now me21n
try to create manually, it will throw error, as not possible to create PO
without reference doc (PR).
Regards
KK

Windows Installer repair issue for per-user folders/files

Intro:
I have doubts that this is the right place to ask about this, since this issue has existed for me on many windows platforms, please suggest where this should be forwarded if this is an inappropriate place to ask.
Please do not be confused by the directory paths for XP, this issue is also true for Windows 7.
Description:
Windows Installer does not repair files in per-user directories, such as [AppDataFolder], when initial installation is performed using system account (for example - distributing the package through SCCM or using psexec) and repairing under a user with administrative
privileges (limited user repair works fine).
Example.
.msi installation installs a custom .xml configuration file to "[AppDataFolder]". We're installing .msi by using psexec /s. log output:
MSI (s) (D8:F0) [15:19:01:214]: Executing op: FileCopy(SourceName=SETTIN~2.CON|customXML,SourceCabKey=customXML,DestName=customXML,Attributes=16384,FileSize=2633,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPart1=-1992414570,HashPart2=1238809189,HashPart3=-80616146,HashPart4=146746036,,)
MSI (s) (D8:F0) [15:19:01:214]: File: c:\WINDOWS\system32\config\systemprofile\Application Data\customXML;
To be installed; Won't patch;
No existing file
MSI (s) (D8:F0) [15:19:01:214]: Source for file 'customXML' is compressed
MSI (s) (D8:F0) [15:19:01:230]: Note: 1: 2318 2: c:\WINDOWS\system32\config\systemprofile\Application Data\customXML
When a user with administrative credentials accesses the advertised shortcut repair is run on the component that has the .xml configuration file, event viewer has an entry about this.
The verbose repair log file shows the following entry:
MSI (s) (D8:E4) [15:22:27:667]: Executing op: FileCopy(SourceName=SETTIN~2.CON|customXML,SourceCabKey=customXML,DestName=customXML,Attributes=16384,FileSize=2633,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=16908288,HashOptions=0,HashPart1=-1992414570,HashPart2=1238809189,HashPart3=-80616146,HashPart4=146746036,,)
MSI (s) (D8:E4) [15:22:27:667]: File: c:\WINDOWS\system32\config\systemprofile\Application Data\customXML;
Won't Overwrite; Won't patch;
Existing file is unversioned and unmodified - hash matches source file
Limited user repair log reads:
MSI (s) (78:8C) [15:26:27:406]: Executing op: FileCopy(SourceName=SETTIN~2.CON|customXML,SourceCabKey=customXML,DestName=customXML,Attributes=16384,FileSize=2633,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=16908288,HashOptions=0,HashPart1=-1992414570,HashPart2=1238809189,HashPart3=-80616146,HashPart4=146746036,,)
MSI (s) (78:8C) [15:26:27:406]: File: c:\Documents and Settings\test\Application Data\customXML;
To be installed; Won't patch;
No existing file
Your suggestions will be very much appreciated.

Hello,
Did you ever get to the root cause of this?
I have a similar problem with a custom XML that is reported as "empty or is not a xml file." in the logs.
Wondered if you had found the root cause?
Kind regards,
Sio.

Purchase documents per user

Similar Messages

Maybe you are looking for