Trace in Purchase Order

I posted a PO with a payment term XY01 "Payment due immediately".
After that, the description of the Payment term was changed to XY01 "Terms to be agreed later".  In other words, the PO was not changed in any manner as the Payment terms is same as XY01 (we had changed only the description of the payment term from FI Side).
Now, I want to know how we can trace that payment description change from MM side with respect to the PO ?

Hi nikkitha,
The description for the payment term can only be changed in the customising.
As R.Rasumalla is mentioning, go to SPRO > Materials Management > Purchasing > Vendor Master > Define Terms of Payment
Once you are there, make double click into your payment term u201CXY01u201D.
In the next screen, select from the Menu: Utilities > Change Requests (Organizer) and you will see all the transports related to this payment term. Then, you need to check what transport made the change into the description and who made this.
Or, you can select from the Menu: Utilities > Change Logs and execute the next screen. There, you will see the changes made to the table T052.
But, this is only working if you have active the storing of logs into your system.
I hope this help.
Kind regards,
Sandra

Similar Messages

  • Production order and its Purchase order after MRP

    Dear Expert,
    I am wondering does SAP B1 2007 provides functionality about a production order and its purchase orders generated after a MRP will be marked so that I can check the corresponding purchase orders of a production order ?
    Thanks,
    Deckard

    Hi Suraj V ,
    Thanks for the reply, I have more questions about,
    (1) is it possible to trace those purchase orders from the production order?
    (2) is it possible to reserve those purchase orders of a production order because I found that the system allow another production orders to take the inventory by the receipt of the purchase orders marked by the other production orders?
    Thanks a lot
    Deckard

  • How to trace purchase order number with respect to Purchase requestion numb

    Hi friends,
    Can u please help me how to Trace purchase order number with respect to purchase Requetuion  number. Is there any standard report  available in R/3

    Hi Vamsi,
    Thats what!!!
    Goto SE16 - EBAN - Give PR number in the iput screen.
    In the output screen you will have to do field selection from Menu - Settings - formatlist - choose fields.
    There you choose Purchase Order.
    So the output will display for you POs for the PR that you entered.
    Regards,
    Vishal

  • At the time of Purchase order creation Material specification how to trace

    Dear all,
    I have an one issue,
    when ever i am creating Purchase order for any material to vendor, the particular material quality specification or Ins plan automatically to flow to purchase order.
    how to address this issue, wheather it is possible or not
    Regards,
    s.sakthivel

    Hi,
    For your requirement only for viewing the data I suggest you to go for below options
    1) In mtrl master itself there is one option Inspection text, here u can maintain the main values so thst during PO
    you can refer these values (To find this click on aditional data tab in mtrl master and inspection long text)
    2) Prepare one report by fetching all the inspection values from below tables so that u can aslo refer this report
       PLKO Inspection plan Header 
       MAPL Material Assignement 
       PLPO Operation Details 
       PLMK Inspection plan characteristics 
       PLMW MAPL-Dependent Charac. Specifications (Inspection Plan) 
    Regards
    Shiva

  • Purchase order and agreement problem

    Hi gurus,
    I have a problem that i've come up with going though event trace on my DEV test system.
    Although, simulation of WF's are fine and all bindings and syntax checks are without error or warnings,
    trace is the only place i've found that something was wrong, appart from that my WF 'WS90200003'
    stopped functioning because of automatic linkage deactivation.
    I had to manually disable automatic linkage deactivation upon error in SWETYPL to keep the WF alive.
    When i did this, all was fine, queing of events started.
    Upon creating purchase order i got following trace:
    BUS2012     RELEASESTEPCREATED     12.05.2008     11:22:07     WS90200003     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
    QCYBUS2012     CREATED     12.05.2008     11:22:08          @AI@     No receiver entered
    BUS2011     QUOTATIONCREATED     12.05.2008     11:22:08          @AI@     No receiver entered
    BUS2012     RELEASESTEPCREATED     12.05.2008     11:22:08     WS90200003     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
    BUS2012     RELEASESTEPCREATED     12.05.2008     11:22:10     WS90200003     @AI@     Event put in queue
    BUS2012     RELEASESTEPCREATED     12.05.2008     11:22:10     WS90200003     @5C\QFeedback after error@     Feedback after error
    FREBUS2012     CREATED     12.05.2008     11:22:08          @AI@     No receiver entered
    Upon creating contract i got following trace, quite similar to one before:
    BUS2014     RELEASESTEPCREATED     12.05.2008     11:34:31     WS90200004     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
    QCYBUS2012     CREATED     12.05.2008     11:34:31          @AI@     No receiver entered
    BUS2011     QUOTATIONCREATED     12.05.2008     11:34:31          @AI@     No receiver entered
    BUS2012     RELEASESTEPCREATED     12.05.2008     11:34:31     WS90200003     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
    BUS2012     RELEASESTEPCREATED     12.05.2008     11:34:31     WS90200003     @AI@     Event put in queue
    BUS2012     RELEASESTEPCREATED     12.05.2008     11:34:31     WS90200003     @5C\QFeedback after error@     Feedback after error
    FREBUS2012     CREATED     12.05.2008     11:34:31          @AI@     No receiver entered
    There are no duplicate entries in 'SWETYPL', agent assignments seem fine, WF customizing is OK.
    Somehow it is not clear for me why or how my 'WS90200003' with BUS2012 keeps triggering.
    When i look in 'Feedback after error' message i see that release code is missing for BUS2012, but weird thing is
    that in contract creation it tries to pass contract document number in event BUS2012...
    I don't know why BUS2012 is constantly double-triggering.
    Not to forget, i'm working on ECC 6.0.
    Thank you for the contribution and tips.
    Greets,
    Tom

    Hi,
    I am using multi-step release strategies, but i'm not sure what you mean...
    Aren't release codes determined from customizing upon saving the document?
    I've checked the customizing and there is only 1 release code that can be
    used by the agent who gets workitem.
    In "Feeback afrer error" log in second calling of BUS2012 there is no release code at all...
    Regards, Tom

  • Message change for invoice amount against Purchase order

    Hi Experts ,
    In MIRO , While invoice posting against a purchase order , when enter is pressed after supplying posting date amount
    Purchase order no and line item no , a message appears : downpayments against vendor xxx exists giving total amount against the vendor indicated in purchase order .
    Can message be changed and amount against that particular purchase order only be displayed instead of against vendor , because same vendor can have multiple purchase order by using any enhancement .
    Thanks
    SA

    Hi SA ,
    i think u are getting this from from ur User Exits only , trace this message based on the message No.
    in standard MIRO u wont get this kind of messages.
    regards
    Prabhu

  • ESYU: Importing Standard Purchase Orders에서 문제 발생시 진단 방법

    Purpose
    Oracle Purchasing - Version: 11.5.10.2 to 12.0.6
    Information in this document applies to any platform.
    ConcurrentProgram:POXPOPDOI - Import Standard Purchase Orders
    이 문서는 reader게 Importing Standard Purchase Orders 실행 중 갑자기 발생하는 issue에 대해 어떻게
    대응하는지에 대한 자세한 정보를 제공한다.
    Instroduction
    Purchase Document Open Interface는 다량의 Standard Purchase Order는 Oracle Purchasing으로 빨리
    import 할 수 있게 한다. Import process는 import 되어야 하는 document information을 PO interface tables에
    넣어주는 작업을 필요로하며, data를 validate 하고 application에 PO를 생성하거나 error message를 return 하는
    Import Standard Purchase Orders concurrent program을 실행한다.
    이 문서의 목적은 Importing Standard Purchase Orders에 관련된 process를 이해하거나 갑자기 발생한 문제의
    원인을 찾는데 도움을 주기 위함이다. PO import 문제는 일반적으로 interface tables에 입력된 불일치하는 data가
    원인이며, 일단 문제가 확인되면 Metalink는 비슷한 문제를 찾아주거나 Oracle Support에 Service Request를 log
    할 수 있다.
    Test case Information
    1. 아래 insert 문장을 이용하여 PO interface tables에 data를 입력:
    INSERT INTO po.po_headers_interface
    (interface_header_id,
    action,
    org_id,
    document_type_code,
    currency_code,
    agent_id,
    vendor_name,
    vendor_site_code,
    ship_to_location,
    bill_to_location,
    reference_num)
    VALUES
    (apps.po_headers_interface_s.NEXTVAL,
    'ORIGINAL',
    207, -- Seattle
    'STANDARD',
    'USD', -- Your currency code
    24, -- Your buyer id stock
    'Advanced Network Devices',
    'FRESNO',
    'V1- New York City', -- Your ship to
    'V1- New York City', -- Your bill to
    'Currency test') -- Any reference num
    INSERT INTO po.po_lines_interface
    (interface_line_id,
    interface_header_id,
    line_num,
    shipment_num,
    line_type,
    item,
    uom_code,
    quantity,
    --unit_price,
    promised_date,
    ship_to_organization_code,
    ship_to_location)
    VALUES
    (po_lines_interface_s.nextval,
    po_headers_interface_s.currval,
    1,
    1,
    'Outside processing',
    'Flooring OSP',
    'Ea',
    1,
    --17.50,
    '10-APR-2009',
    'V1',
    'V1- New York City' )
    INSERT INTO po.po_distributions_interface
    (interface_header_id,
    interface_line_id,
    interface_distribution_id,
    distribution_num,
    quantity_ordered,
    charge_account_id)
    VALUES
    (po_headers_interface_s.currval,
    po.po_lines_interface_s.CURRVAL,
    po.po_distributions_interface_s.NEXTVAL,
    1,
    1,
    12975) -- Your Charge Account Id
    2. Interface tables에 data가 insert 되었다면 import progra을 실행전 정보를 확인하기 위해 아래 query 문을 이용한다.
    a - Select * from PO_HEADERS_INTERFACE where INTERFACE_HEADER_ID=&headerid
    b - Select * from PO_LINES_INTERFACE where INTERFACE_HEADER_ID=&headerid
    c - Select * from PO_DISTRIBUTIONS_INTERFACE where INTERFACE_HEADER_ID=&headerid
    3. Data를 review 했으면 Import Standard Purchase Orders program을 실행한다.
    Parameter >>
    Default Buyer: Null
    Create or Update Items: No
    Approval Status: INCOMPLETE
    Batch Id: Null
    4. 만일 program에 문제가 있어 error가 발생한다면 error의 원인을 제공하기 위해 Purchasing Interface Error Report를
    실행할 수 있다.
    Parameter >>
    Source Program: PO_DOCS_OPEN_INTERFACE
    Purge Data: No
    만일 PO가 import 되지 않았다면 Puchasing Interface Errors Report와 동일한 정보를 보기 위해 Interface Errors table을
    아래 SQL을 이용하여 조회할 수 있다.
    SELECT * FROM PO_INTERFACE_ERRORS WHERE INTERFACE_TRANSACTION_ID ='&recordsinterfacetransid';
    Diagnostics
    Import Standard Purchase ORder process의 troubleshoot 도움을 위해 아래 Diagnostics과 Reports를 이용한다.
    1. Diagnostics Tool : Oracle Purchasing Purchasing Documents Open Interface Data Collection Test
    (please refer to Note 224887.1 for assistance)
    이 Diagnostics는 import program에 의해 import 되는 data를 validate 할 것이며 missing 되거나 맞지않는 정보를 highlight 한다.
    이 Tool은 interface tables에 있는 맞지 않거나 불완전한 data의 자세한 정보를 제공할 수 있다.
    Error는 PO를 import 할 때 발생한 문제 분석을 시도하는데 매우 유익하므로 SR을 log시 이 Diagnostic output을 upload 하는
    것을 권장한다.
    2. Purchasing Interface Errors Report
    이 report는 Oracle Purchasing에서 사용가능하며 Import Standard Purchase Orders program을 실행시 발생하는
    error를 강조한다.
    Tracing
    11.5.10 이상의 version에서 Import Standard Purchase Orders program의 trace를 생성:
    1. Navigate to System Administrator responsibility
    2. Navigate to Profiles->System
    3. Query the Profile Option Concurrent: Allow Debugging and set it to Yes at User level
    4. Navigate to Purchasing responsibility
    5. From the Requests form, choose the Import Standard Purchase Orders program and set the required Parameters
    6. Click the Debug button
    7. Check the SQL Trace checkbox and specify Trace with Binds and Waits
    8. Submit the Concurrent program
    9. Retrieve the trace file created.
    Logging
    Import Standard Purchase Orders program의 FND Deug Log 생성:
    1. Log_seq를 아래 SQL을 이용하여 확인.
    select max(log_sequence) from fnd_log_messages;
    2. Set the following profiles at the user level:
    FND: Debug Log Enabled = YES
    FND: Debug Log Filename = NULL
    FND: Debug Log Level = STATEMENT
    FND: Debug Log Module = %
    3. Run Import Standard Purchase Orders program
    4. Using a SQL client run the following query :
    Select * from fnd_log_messages
    where log_sequence > &log_seq_noted_above
    order by log_sequence;
    이 query의 output은 Import Standard Purchase Orders program이 실행 중 발생한 error를 표시한다.
    Reference
    Note 781351.1

  • Error while doing miro of network purchase order ( no funds center entered/

    Hi,
    we are facing one problem while doing miro of network  service purchase order. System is giving message 'No funds center entered/derived in item 00030'.
    We have activated funds management in Jul'10. The said network service PO belong to previous year. Also we have changed
    commitment item of GL account related to concerned service order in Jul'10 & posted GRN one in apr'10 & one aug'10.
    System is not allowing to cancel the service entry sheet.
    Can anybody help on this.
    regards
    abhishek

    we had activated the trace facility for FMDEIRIVE & found that all FC/Commitment item derived correctly. But while posting the document it is throwing an error.
    Regards
    Abhishek

  • DBIF_RSQL_INVALID_RSQL when creating a Purchase Order (ME21N)

    Hi,
    The system is generating a short dump DBIF_RSQL_INVALID_RSQL when a user tries to create a purchase order.
    what could be the cause of this? i have analysed the short dump in st22 and looked at sm21 and st11 and they are giving very little detaill.
                                                                                    Error in the module RSQL accessing the database interface.                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLZMM_GET_ACT" had to be terminated because one of    
    the                                                                               
    statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                                                               
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                          
    and make a note of the actions and input that caused the                          
    error.                                                                               
    To resolve the problem, contact your SAP system administrator.                    
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer          
    termination messages, especially those beyond their normal deletion              
    date.                                                                               
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below  
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was  
    neither                                                                  
    caught nor passed along using a RAISING clause, in the procedure          
    "ZMM_GET_ACT_PLN" "(FUNCTION)"                                           
    Since the caller of the procedure could not have expected this exception  
    to occur, the running program was terminated.                            
    The reason for the exception is:                                          
    The SQL statement generated from the SAP Open SQL Statement violates a    
    restriction imposed by the database system used in R/3.                                                                               
    Possible errors:                                                          
    o The maximum size of an SQL statement has been exceeded.                
    o The statement contains too many input variables.                       
    o The space needed for the input data exceeds the available memory.      
    o ...                                                                               
    You can usually find details in the system log (SM21) and in the          
    developer trace of the work process (ST11).                               
    If an error occurs the developer trace often informs you about the        
    current restrictions.                                                                               
    How to correct the error                                                                               
    The exception must either be prevented, caught within the procedure             
    "ZMM_GET_ACT_PLN"                                                              
    "(FUNCTION)", or declared in the procedure's RAISING clause.                    
    To prevent the exception, note the following:                                   
    The SAP Open SQL statement must be divided into several smaller units.          
    If the problem occurred due to the use of an excessively large table            
    in an IN itab construct, you can use the addition FOR ALL ENTRIES               
    instead.                                                                        
    When you use this addition, the statement is split into smaller units           
    according to the restrictions of the database system used.                                                                               
    You may able to find an interim solution to the problem                         
    in the SAP note system. If you have access to the note system yourself,         
    use the following search criteria:                                                                               
    "DBIF_RSQL_INVALID_RSQL" CX_SY_OPEN_SQL_DBC                                     
    "SAPLZMM_GET_ACT" or "LZMM_GET_ACTU01"                                          
    "ZMM_GET_ACT_PLN"                                                               

    Hi,
    Wherever you have used SQL statement please do check all the fields here as some of the fields are not in correct order as they are required per the actual table in dictonary, to just verify that you can use addition of "INTO CORRESPONDING FIELDS OF INTERNALTABLE" in your SQL statement as this will not require the fields to be in order but this may cause performance issue.
    Thanks and Regards
    Sudharshan

  • Problem by creation of purchase order

    Hi guys,
    after implementing SP 9 and 10 we are not longer able to create purchase orders automatically with WF WS14000075. In transaction bbp_pd we get the error message
    "System  of purchasing organization XXX differs from target system XXX". But we have assigned our product categories for the relevant backend system to the purchasing groups. We also wanted to implement the notes 913831 and 832097 with transaction snote but we could not because these notes were already implemented. In transaction bbp_pd the status for Workflow WS14000075 is "Waiting".
    Thanks in forward for your help. We appreciate your help a lot.
    BR,
    Bernd

    Hi Yann,
    i have checked the WF14000075 with transaction SWUD. After I have created an event with the user who has created the SC I have checked the Display of event traces. There the following error message appears:
    "Check FM with exception",
    Event Instance ID    16067
    Object Type          BUS2201
    Object Key           7100000124
    Event                SAVED
    Event Creator        US PROD1          PEK
    Creation Time        23.11.2006 14:12:19 CET
    Receiver Type        WS14000075
    Object Key
    Receiver FM          SWW_WI_CREATE_VIA_EVENT_IBF
    RFC Destination      WORKFLOW_LOCAL_010
    Check FM             SWB_CHECK_FB_START_COND_EVAL
    Receiver Type FM
    Message              Operator 'LT': The value of the left operand cannot be determined
    Trace Date/Time      23.11.2006 14:12:20 CET
    User Name            PROD1          PEK
    Main Program         SAPLSWUS
    Action               Check FM ends with exception
    BR,
    Bernd

  • No Matching Record Found 'CRD1' at the time of Purchase Order Creation

    Hi !
    I have transferred business partners record through DTW 2005.0.17 in SAP B1. Now when I go to make purchase order, at the time of selecting business partner, It gives error msg. No matching record found 'CRD1'. I have checked the table CRD1, there the data exists. And when i modify business partner's address through business partner form, the problem is solved. I am not able to trace which value i am missing at the time of data transfer.
    can anyone help?
    Anupam Negi
    [email protected]

    thanks jimmy,
    I tried as per your suggestion, i deleted the following tables OCRD,ACR1,ACRB,ACR3,CRD1,ACRD,ACR2,CRD2,CRD5,CRD3,CRD7, then again imported the BP records. Its still giving the same error. I have imported the Business Partner Main template & Business partner Address template. Is it neccassary to import all other templates i.e. BPNankAccount,BPPaymentDate,BPPaymentMethod,ContactEmployees

  • Error in Email PDF of purchase order

    In the purchase order, we have set up a message(output) type as
    external send for sending the email to the buyer. It has been working
    good for the past 1 year and suddenly for the past few weeks we started
    noticing errors.
    The error is that we cannot see any data in one of the pages of the PO
    output(PDF attachment). For example, if a PO has 5 pages, the 2nd page
    will be blank and all the other pages would have come out fine. This
    does not happen in every PO and also it is not the same page which is
    missing in all the error PO PDFs. But when we print the output with
    the Print medium it always looks fine. Both uses the same smartform
    and the program.
    Even in the same PO, the first time they email it does not work
    correctly and if they repeat the output after a few minutes all pages
    look fine.
    This error happens sporadically and it does not have any connection
    with the number of pages a PO prints or it is not the same page that is
    missing always. I beleive it does not have anything to do with the
    special characters in the PO. The language we are trying to print is
    English.
    We use CONVERT_OTF function module to convert from OTF to PDF. This
    was working good always before and suddenly we see problems every now
    and then. I will also attach a screen shot of the error when the PDF
    is opened(this shows a page in PO which is blank & error of PDF). Can
    you please look into this and direct us in the right path
    to solve the issue?
    Thanks

    Hi,
    As mentioned the pdf missing page error is sporadic, I would recommend you to check the following:
    1. Add a delay 'WAIT' Function Module before 'CONVERT_OTF'. Maybe, due to some change in hardware, patch upgrade or increased user load, the pdf is not getting generated the first time. Hence, it works fine the next time.
    2. Ask your BASIS Team to monitor the dialog processes when you run this activity. You can also use SQL Trace to get any leads with reference to bandwidth issues.
    Regards,
    Pranav.

  • Asset cost center assignment missing in purchase req or purchase order

    Has anyone else ever encountered this? 
    When we create a purchase requsition for assets, the cost assignment is determined from the existing asset. Most assets bring over the cost center into the account assignment. A few do not.  FMDERIVE shows the cost center populated when tracing. When you exit the derivation trace, the cost center is missing from the purchase requeistion or purchase order line item.  Any ideas? 
    PS: THis happens whether or not the asset has an entered serial number.
    Any thoughts of what to check are appreciated.
    Bob

    No, our FMDERIVE defaults Funds Center from Cost Center, which IS occurring, and, as stated above, the cost center appears correctly as expected on the FMDERIVE trace screen.. 
    Added info: In our test system we have reconfigured the ME51N entry screen to allow manual input of the cost center.  It is STILL automagically cleared during the save/validation process.
    Thanks for your question!
    Bob

  • Purchase Order created in status expired

    Hi,
    we use SRM 7.0. After orderering a shopping cart and successful SC approval the purchase order is immediately displayed in status "expired". The PO can not be changed; there is no approval data. Event trace SWEL shows no entry /SAPSRM/CL_WF_PDO_PO READY_FOR_WORKFLOW.
    Do you have any ideas on this behaviour?
    Best regards,
    Frank

    Hi Frank,
    I do not think PO has a staus "Expired".
    There might be some development done in your organization.
    My guess is delivery date might have been expired and your project team might have developed to show that as "expired" (my wild guess...)
    Pl verify.
    Best regards,
    Ramki

  • Purchase order history standard datasource

    Hi All
    Is there a standard datasource for purchase order history- table EKBE, I need to pick history with movement types
    Thanks

    Hi,
    Chk this links...
    http://help.sap.com/saphelp_nw70/helpdata/EN/58/f6383fdb800804e10000000a114084/frameset.htm
    and also trace thru left panel...
    rgds,

Maybe you are looking for