Indent Purchase Order

Dear All
What is meant by Indent PO?  How it is raised? If I want to delete the Indent PO how can I do it?
Note:  During deleting Indent PO I am getting error saying CHECK FOR THE PAYMENT TERMS IN HEADER error no:Y210,
How to overcome this error and delete the Indent PO?
Regards
Srini

hi,
The PO which is generated from the indent PR is called indent PO...
For indent PR features check the following thread:
Indent Creation
Hope it helps...
Regards
Priyanka.P

Similar Messages

  • Release Procedure in Indent/Purchase Order

    I want to customise release strategy in indent and Purchase order in SAP. Kindly provide me steps to configure this. will apperitiate your efforts.
    Manjit

    Hi Manjit,
    Release Procedure for Purchase Orders
    In this section, you set up a release procedure for purchase orders (POs).
    Requirements
    If you want to use workflow to release POs, you must make the standard and basic settings for workflow (Basis -> Business Management -> SAP Business Workflow).
    How do you set üp a release procedure for POs?
    To set up the release procedure, you must make a series of settings in Customizing. This section provides you with an overview of the necessary activities.
    You must perform the following steps:
    1. Create characteristics and classes
    For more on this topic, see Edit Characteristics and Edit Classes.
    Note
    If you wish to link your release procedure to workflow, you must perform steps 2 and 3 . You make these settings in Customizing for Business Workflow (Basis -> Business Management).
    Otherwise, continue with step 4.
    Define organizational plan
    For more on this topic, see Edit Organizational Plan.
    Assign standard tasks and activate event-receiver linkage.
    For more on this topic, see Perform Task- Specific Customizing.
    1. Set up release procedure for RFQs
    a) Create release group
    b) Create release code
    c) Create release indicator
    d) Create release strategy
    Note
    You need only carry out the following step if you wish to link your release procedure to workflow.
    e) Assign release code to a user
    For more on this topic, see Define Release Procedure for POs.
    2. Check release strategies
    For more on this topic, see Check Release Strategies.
    Further notes
    For more information, refer to
    · Implementation of a Release Procedure for Purchasing Documents
    · Release of Purchasing Documents (SAP Library -> Basis -> Business Management (BC-BMT) -> SAP Business Workflow (BC-BMT-WFM) -> Reference documentation -> BC Workflow Scenarios in the Applications -> MM Materials Management: Workflow Scenarios)
    Edit Characteristic (CT04)
    In this step, you create characteristics for a release procedure for purchase orders (POs).
    Classification characteristics are the criteria for a release condition. If the criteria of a release condition are satisfied, the associated release strategy is assigned to the purchasing document (e.g. purchase order or RFQ).
    Example
    Release condition for release strategy EA:
    Characteristic Characteristic value
    Total net value of PO Above $10,000
    If the total value of a purchase order exceeds $10,000, release strategy EA is assigned to this PO.
    Requirements
    In communication structure CEKKO you will find all the fields that can be used as characteristics for a release condition (e.g. BSART for the order type and GNETW for the total order value).
    Check which fields you wish to use as characteristics for your release strategy. To do so, choose Tools -> ABAP Workbench -> Development -> Dictionary, enter CEKKO in the field Database table , and choose "Display".
    Note
    If you wish to define a separate release strategy for the various document categories (PO, RFQ, etc.), you must create a characteristic for each relevant document category.
    Activities
    1. Create a characteristic for each field from communication structure CEKKO that is to be a criterion for your release strategy. You have a free choice of names for the characteristic.
    2. Enter the table name and the field name on the tab page Additional data (for example, table CEKKO for field GNETW).
    Note
    o Do not select any of the indicators in the area Procedure for value assignment on the tab page Additional data. Only if none of these indicators is marked can you assign a value or value interval to the characteristic when defining your release strategy.
    o When you create a characteristic for a currency-dependent field (e.g. GNETW), a box appears in which you must enter the currency for the relevant value. The system then converts the currency of the purchasing document into this currency.
    3. Check the data for the chosen field on the tab page Basic data.
    If you want to enter several values or a value interval for a characteristic, set the Multiple values indicator in the area Value assignment.
    Note
    Value intervals can only be specified for numerical values (e.g. an interval of $10,000 to $15,000 for the value of the purchase order.
    4. Check the texts for the field on the tab page Descriptions.
    5. You can maintain default values for a characteristic on the tab page Values.
    If you maintain values here, these values will be displayed as input help under Create Procedure with Classification -> Release Strategy -> Classification . If you wish to use not only the input help but also other values, you must select the Additional values indicator.
    Note
    You can also maintain ' ' as a default value. For example, for account assignment: ' ' for stock material, 'k' for cost center, and 'a' for asset.
    6. If you want to restrict the use of a characteristic to particular class types, specify the relevant class types on the tab page Restrictions. For example, class type 032 for the release strategy.
    Further notes
    Further information on characteristics is available in this Customizing activity via Help -> Application help.
    Customer exits
    Customer exit M06E0004 enables you to change the communication structure for determining the release strategy for purchasing documents.
    Edit Class( CL02 )
    In this step, you create classes for a release procedure for purchase orders (POs).
    You use a class to group together characteristics that are to constitute a release condition for a release strategy. In the step "Define Release Procedure for Purchase Orders " you assign this class to the release strategy.
    Activities
    1. Create a class with the class type 032. You have a free choice of names for the new class (e.g. REL_RFQ for the release of RFQs).
    2. Assign a name for the new class on the tab page Basic data.
    3. You can view an error message if different characteristics with identical values have been assigned to a class. To be able to do so, select the Check with error message indicator in the Same classification area.
    4. If appropriate, select terms to be used as search criteria in searches for your class on the Keywords tab page.
    5. Assign your characteristics to the class via the tab page Characteristics.
    Further notes
    Further information on classes is available in this Customizing activity under Help -> Application help.
    Define Release Procedure for Purchase Orders
    In this step, you set up the release procedure for purchase orders (POs) and can link it to workflow. (Note that in this context "releasing" means "approving", or giving the "green light" to a document.)
    Requirements
    · In the case of a release procedure linked to workflow, you must have previously created the user names, positions, jobs, etc. that you here assign to the release code in the organizational plan and must have linked them to the relevant standard tasks in task-specific Customizing (Basis -> Business Management -> Business Workflow -> Perform Task-Specific Customizing).
    · You must assign the authorization M_EINK_FRG to the persons who are to be involved in the release procedure ( Authorization Management -> Create Authorization Profiles and Assign to Users).Activities
    Here you define the following:
    ·     Release group
    ·     Release codes
    ·     Release indicator
    ·     Release strategy
    ·     Workflow
    Release group
    Create a release group for your release procedure and assign it to a class. In the process, you assign release conditions to the release procedure.
    Release codes
    Here you create the release codes you need for your release strategy and assign the codes to your release group. If a release code is to be used in workflow, indicate this accordingly in the Workflow field
    The Workflow indicator is also used to control role resolution:
    ·     "1 - Role Resolution with Group, Code and Plant (T16FW)"
    Here you use a role resolution that is supplied in the standard system. To do so, you must assign the release point in the section Workflow (see below).
    ·     "9 - Role Resolution via User Exit"
    Here you use the customer exit M06E0005 to define a role resolution of your own.
    Release indicators
    A release indicator shows the release status of a PO.
    Via the following settings, you can define the release indicators you need for your release procedure:
    ·     The Released indicator is used to specify whether messages (PO documents in output format) may be transmitted for a purchase order with this indicator.
    ·     The Changeability indicator shows the effect of changes to the PO (a change to a PO may require a new release strategy to be determined, for instance).
    ·     By means of the Value change indicator, you can specify that the release strategy is to be re-started if a PO is changed and the value of a PO item thereby increases by a certain percentage (e.g. 10%). Set the Changeability indicator to "4 - Changeable, new release in case of new strategy or value change" or "6 - Changeable, new release in case of new strategy or value change/outputted" and enter a percentage in the Value change field.
    Attention:
    The following release indicators are necessary for every release procedure:
    o     Release indicator for initial status
    If the PO is subject to a release strategy, it must normally be released before it can be transmitted to the vendor. Therefore, when a PO is created, it is assigned a release indicator that blocks it from being outputted in message form.
    The Released indicator must not be selected for this indicator.
    o     Release indicator for released status
    This indicator is assigned to the PO when it is released.
    The Released indicator must be selected for this indicator.
    Release strategies
    Create a release strategy for your release group and assign your release codes accordingly.
    ·     Release prerequisites
    With the release prerequisites , you specify the order in which the individual release points (individuals or departments) represented by the release codes may release the document.
    Example
    The following table shows release prerequisites for a strategy with four release codes.
    Code/Release prerequisite
              01     02     03     04
         01     -               
         02          -          
         03               -     
         04                    -
    In this release strategy, the codes 01, 02, 03, and 04 must successively release the purchase order.
    Read the table from left to right. For instance, the third line for release code 03: For code 03, release via code 01 and code 02 is a prerequisite. That is to say, the PO must be released via codes 01 and 02 before it can be released via code 03.
    ·     Release statuses
    Here you specify the status a PO has after certain release points have effected release.
    Specify which release indicator/status a PO is to have after having been released via a certain release code.
    ·     Classification
    In classification, you maintain the values assigned to the characteristics. Via the characteristics and their values, you specify the POs to which your release strategy is assigned.
    Maintain values (individual values or intervals) for your characteristics.
    Example
    Two characteristics and their values have been maintained in classification for release strategy 'EA':
    - Document type - 'NB - standard purchase order'
    - Total value - above $10,000
    All POs with the document type 'NB' and a total value in excess of $10 ,000 are thus subject to a release procedure with the release strategy 'EA'.
    ·     Release simulation
    The release simulation function enables you to check which status a PO will achieve with your release strategy if release is effected by a certain release point.
    Choose "Simulate release" and release the document with the desired release code by double-clicking. The system shows you which status the PO now has as a result of this release.
    Workflow
    Assign a processor ID to your workflow-relevant release codes. The processor (member of staff responsible for processing the document) will then receive a work item when he or she is required to effect release.
    You can assign a processor ID either directly or indirectly:
    o     Direct processor assignment:
    Enter a user name.
    o     Indirect processor assignment:
    Enter a job, for example, or a position. At runtime, the system will then determine the member(s) of staff responsible for processing the document.
    Customer exit
    Customer exit M06E0005 enables you to define your own role resolution which determines the person responsible for releasing purchasing documents in workflow.
    Further notes
    Further information on how to set up a release procedure linked to workflow is available via the menu options Help -> Application Help.
    Check Release Strategies
    In this step, you can check whether the basic settings for your release strategy are complete and correct.
    Checks
    The following checks are carried out for purchasing documents:
    ·     Basic checks
    The system checks whether the necessary release groups exist in the system. For example: Whether a release group has been deleted even though an associated release strategy still exists.
    ·     Checks regarding release groups and release classes
    The system checks whether the release groups and the assigned classes have been maintained correctly. For instance, whether
    o     A class has been assigned to the release groups and whether it exists in the system
    o     Characteristics - which exist in the system and are linked to the communication structure - have been assigned to the class
    o     A customer exit must be maintained for a characteristic
    ·     Checks regarding release codes
    The system checks whether the release codes have been maintained correctly
    ·     Checks regarding release indicators
    The system checks whether the release indicators have been maintained correctly. For example: Whether release indicators exist for the statuses "Blocked" and "Released".
    ·     Checks regarding release strategies
    The system checks whether the release strategies have been maintained correctly. For example, whether:
    o     Release codes have been assigned to the release strategy
    o     The relevant release indicators have been assigned to the initial and final statuses of a release strategy
    ·     Checks regarding link to workflow
    The system checks whether the link between your release procedure and workflow has been maintained correctly. For example, whether:
    o     A processor (member of staff responsible for processing) has been assigned to a workflow-relevant release code and is defined in the organizational plan
    o     A customer exit is necessary for the role resolution
    Result
    The result of these checks is displayed in a log. Further information is available in the Customizing activity under Help -> Application Help.
    Activities
    1. Start the check by performing the Customizing activity.
    2. Check whether any error or warning messages are displayed.
    3. If necessary, correct your Customizing settings for the release procedure.
    4. Re-run the check after making corrections.
    Rewards if Helpful
    Regards
    Sanjay L

  • Help on Indent Sales Order Creation - Missing Items in Purchase Requisition

    Hi Experts,
    We have Indent Sales setup where when we create Indent Sales Orders it will also create Purchase Requisitions. But we have encountered a lot of of missing items in the Purchase Requisition that are in Indent Sales. Have you encountered this kind of behavior? What are the usual suspects (configuration-wise) for this scenario?
    Thanks for your Help!

    hi,
    please check the SCHEDULE LINES for those PR is getting generated and also for not generating.
    PLEASE CHECK THE SCHEDULE LINE CATEGORY CONTROL FEATURES on the same
    hope this clears your issue
    balajia

  • Open Purchase order pload

    Can any one provide OPen purchase order upload program using BAPI method....
    Thanks & regards.
    Ramesh T.
    Moderator Message : Not enough re-search before posting. Thread locked
    Edited by: Vinod Kumar on Apr 22, 2011 3:41 PM

    Hi Harshad,
    You can use the Service PO scenario.
    Service PO is used to Procure/ Avail the Services. you can create the service PO ( having account Assignment Category 'K' and item Category 'D'  for services) which has the validity period.
    at item overview level, you have to specify the Material /Service info in Short text.
    At Item Detail level, you will have the service tab. Depending on your indent (as and when it comes) you can enter the service item with its unit cost and qty.
    Later on, once you physically received the Material/Service, then using transaction ML81N you can accept the service. which in turn post your GR Document.
    Regards,
    S Anand

  • Purchase Order: Ship to location problem - Please help

    Hi All,
    I have come across a problem when publishing Purchase orders where the PO header ship to address differs to a seperate PO line ship to address.
    I have written the following Choose statement to try and show separate ship to locations for each separate PO line.
    <?for-each:G_LINES?>
    <?choose:?>
    <?when:number(//G_HEADERS/POH_SHIP_TO_LOCATION) = number(//G_SHIPMENTS/PLL_SHIP_TO_LOCATION)?>
    <?POL_LINE_NUM?> <?C_ITEM_DESC?> <?LINE_NOTE?>
    <?end when?>
    <?otherwise:?>
    <?POL_LINE_NUM?> <?C_ITEM_DESC?> <?LINE_NOTE?>
    SHIP TO: <?ADDRESS_LINE1?>
    <?ADDRESS_LINE2?>
    <?end otherwise?>
    <?end choose?>
    <?end for each?>
    my logic is that if the header ship to ID is = to the line items ship to ID then just show some basic PO line info.
    Otherwise if the numbers differ then show the individual lines info along with the additional Ship to address which is in ADDRESS_LINE1, ADDRESS_LINE2 etc.
    And repeat this condition for how ever many PO lines exist for the overall purchase order.
    However, when i publish this the "otherwise" condition never gets checked if the first PO line is TRUE and vis versa if the first PO line is false.
    So if the first PO line is true then every single PO line will just show the When condition even if the separate PO lines ship to ID differs to the POH_ship to id.
    any idea why the otherwise condition wont fall true for the 2nd 3rd or however many PO lines there are if the first PO line is flagged as true?
    I hope this makes sense. Many thanks for any help.
    Greg

    I have a PO that we are using that has basically the same requirements. If the line address is different (any of them) then the header prints a message to "see below" and the address line contains the shipping information.
    The way I have done this was to create a variable and compare to see of any of the lines were different when the header was read. Then check the var when the line is processed. The template is quite long as we have many fields that dynamically display/or not so I will post a truncated version below and also please note that on this form we simply gave up using the Oracle's "fantastic" MSWORD plug-in and had to use pure a XML-FO template. However, I think the portions/logic you need should be transferable into MSWORD if you are careful.
    If snipit of code is not enough let me know and I can try to paste the entire thing after my marathon meeting today <ugh!>.
    --------start code-----------
    <xsl:for-each select=".//G_HEADERS">
    <xsl:variable name="SAME_SHIP_TO_ADDRESS_USED" select="count(.//PLL_SHIP_ADDRESS_LINE1[. != current()/POH_SHIP_ADDRESS_LINE1]) = 0" />
    ...(lots of header stuff goes here)
    <xsl:for-each select=".//G_SHIPMENTS">
    <xsl:if test="$SAME_SHIP_TO_ADDRESS_USED" xdofo:ctx="3">
    <fo:block xdofo:xliff-note="if:shipline, eif, if:shipline, ifCountShip>1, PLL_SHIP_ADDRESS_LINE1" padding-bottom="0.0pt" text-align="start" orphans="2" widows="2" padding-top="0.0pt" end-indent="0.0pt" linefeed-treatment="preserve" start-indent="0.0pt" height="0pt">
    <fo:inline height="7.0pt" font-family="Arial" white-space-collapse="false" font-size="7.0pt">Address at top of page</fo:inline>
    </fo:block>
    </xsl:if>
    <xsl:if test="not($SAME_SHIP_TO_ADDRESS_USED)" xdofo:ctx="3">
    <fo:block padding-bottom="0.0pt" text-align="start" orphans="2" widows="2" padding-top="0.0pt" end-indent="0.0pt" linefeed-treatment="preserve" start-indent="0.0pt" height="0pt">
    <fo:inline height="7.0pt" font-family="Arial" white-space-collapse="false" font-size="7.0pt">
    <xsl:value-of select="PLL_SHIP_ADDRESS_LINE1" xdofo:field-name="PLL_SHIP_ADDRESS_LINE1"/>
    </fo:inline>
    </fo:block>
    ...(lots more address fields here!)
    </xsl:if>
    </xsl:for-each>
    </xsl:for-each>
    ------------end code------------
    Good luck,
    Scott

  • How to add external URL link to SAP object (Purchase Order, Invoice, etc)

    Hello,
    Is there any function module /BAPI that allows me to add an external URL link to a existing Purchase Order
    or Invoice document in R3 system?
    I tried to debug the system but have not found no suitable function module for it.
    I also analyzed the ABAP code of the small GUI window that allows to add a external URL link to
    a Purchase Order, and found the function module SO_OBJECT_INSERT. However I could not debug
    it (seems to be created with BOR objects) so I've no example for it.
    Please help!
    Regards,
    Manuel Dias

    CONSTANTS:
        c_http(36)    TYPE c VALUE '/BpHttpApis/slaphapi?ibmperson/(uid=',
        c_listxml(12) TYPE c VALUE ').list/byxml',
        c_value(5)    TYPE c VALUE 'value',
        c_cn(2)       TYPE c VALUE 'cn',
        c_mail(4)     TYPE c VALUE 'mail',
        c_em_num(19)  TYPE c VALUE 'managerserialnumber',
        c_em_cou(18)  TYPE c VALUE 'managercountrycode'.
      DATA  client          TYPE REF TO if_http_client.
      DATA  url             TYPE string.
      DATA  xbuffer         TYPE xstring.
      DATA  l_value         TYPE zchar2000.
      DATA  l_value_string  TYPE string.
      DATA  content         TYPE string .
      DATA  rows            TYPE STANDARD TABLE OF string.
      DATA  wa_rows         TYPE string .
      DATA  conv            TYPE REF TO cl_abap_conv_in_ce.
      DATA  ixml            TYPE REF TO if_ixml.
      DATA  streamfactory   TYPE REF TO if_ixml_stream_factory.
      DATA  parser          TYPE REF TO if_ixml_parser.
      DATA  istream         TYPE REF TO if_ixml_istream.
      DATA  document        TYPE REF TO if_ixml_document.
      DATA  node            TYPE REF TO if_ixml_node.
      DATA  xmldata         TYPE string.
      DATA  iterator        TYPE REF TO if_ixml_node_iterator.
      DATA  nodemap         TYPE REF TO if_ixml_named_node_map.
      DATA  attr            TYPE REF TO if_ixml_node.
      DATA  name            TYPE string.
      DATA  prefix          TYPE string.
      DATA  value           TYPE string.
      DATA  indent          TYPE i.
      DATA  count           TYPE i.
      DATA  index           TYPE i.
      url = 'http://bluepages.ibm.com'.
      CLEAR: l_value_string, l_value.
    ***Create the HTTP client
      CALL METHOD cl_http_client=>create_by_url
        EXPORTING
          url    = url
        IMPORTING
          client = client
        EXCEPTIONS
          OTHERS = 1.
      IF sy-subrc <> 0.
    Create the HTTP client failure, sy-subrc =
        MESSAGE i005(zm) WITH text-026 sy-subrc.
        EXIT.
      ENDIF.
      CONCATENATE c_http
                  p_accnt
                  p_couty
                  c_listxml
                  INTO l_value.
      l_value_string = l_value.
    ***Get employee information
      CALL METHOD client->request->set_header_field
        EXPORTING
          name  = '~request_uri'
          value = l_value_string.
      client->send( ).
      client->receive( ).
    ***Load to xstring
      CLEAR xbuffer .
      xbuffer = client->response->get_data( ).
      conv = cl_abap_conv_in_ce=>create( input = xbuffer ).
      conv->read( IMPORTING data = content ).
    create the ixml main factory
      ixml = cl_ixml=>create( ).
    create a stream factory
      streamfactory = ixml->create_stream_factory( ).
      xmldata = content.
    create a input stream
      istream  = streamfactory->create_istream_string( string = xmldata )
    create a ixml document
      document = ixml->create_document( ).
    create a xml parser
      parser  = ixml->create_parser( document       = document
                                     stream_factory = streamfactory
                                     istream        = istream ).
    parse the xml document into DOM tree
      IF parser->parse( ) <> 0.
    parse the xml document into DOM tree failure
        MESSAGE i005(zm) WITH text-027.
        EXIT.
      ELSE.
        node ?= document.
        IF node IS INITIAL.
    To be done
        ENDIF.
    create a node iterator
        iterator  = node->create_iterator( ).
    get current node
        node = iterator->get_next( ).
    loop over all nodes
        WHILE NOT node IS INITIAL.
          indent = node->get_height( ) * 2.
          indent = indent + 20.
          CASE node->get_type( ).
            WHEN if_ixml_node=>co_node_element.
          element node
              name    = node->get_name( ).
              nodemap = node->get_attributes( ).
              IF NOT nodemap IS INITIAL.
            attributes
                count = nodemap->get_length( ).
                DO count TIMES.
                  index  = sy-index - 1.
                  attr   = nodemap->get_item( index ).
                  name   = attr->get_name( ).
                  prefix = attr->get_namespace_prefix( ).
                  value  = attr->get_value( ).
                ENDDO.
              ENDIF.
            WHEN if_ixml_node=>co_node_text.
    User name
              IF name  = c_value AND
                 value = c_cn.
          text node
                value  = node->get_value( ).
                p_name = value.
              ENDIF.
    User email
              IF name  = c_value AND
                 value = c_mail.
          text node
                value  = node->get_value( ).
                p_email = value.
              ENDIF.
    Employ serial number
              IF name  = c_value AND
                 value = c_em_num.
          text node
                value  = node->get_value( ).
                p_em_num = value.
              ENDIF.
    Employ country code
              IF name = c_value AND
                 value = c_em_cou.
          text node
                value  = node->get_value( ).
                p_em_cou = value.
              ENDIF.
          ENDCASE.
      advance to next node
          node = iterator->get_next( ).
        ENDWHILE.
      ENDIF.

  • Payment by letter of Credit against Purchase order

    When we are purchasing from Foreign Vendors , we need to open a Letter
    of credit (LC) .
    Depending on the terms of Purchase order , Vendor will discount it /get
    payment from Bank on submitting LC and other necessary documents.
    Vendor's Bank, at appropriate Time will send the same to Customer's Bank
    How to mapped this scenario in SAP-MM and FI .
    Activities required to be updated against Purchase order :
    (1) Payment Terms : 100 % against LC on delivery
    (2) History should reflect LC opened - Date and Bank Name which
    Vendor has suggested, our company's Bank Name
    (3) LC discounted details
    (4) LC payment due date to our company Bank - as Procurement needs
    to inform to Finance for this.
    Any help will be highly appreciated.
    Thanks and Best Regards,

    When we are purchasing from Foreign Vendors , we need to open a Letter
    of credit (LC) .
    Depending on the terms of Purchase order , Vendor will discount it /get
    payment from Bank on submitting LC and other necessary documents.
    Vendor's Bank, at appropriate Time will send the same to Customer's Bank
    How to mapped this scenario in SAP-MM and FI .
    Activities required to be updated against Purchase order :
    (1) Payment Terms : 100 % against LC on delivery
    (2) History should reflect LC opened - Date and Bank Name which
    Vendor has suggested, our company's Bank Name
    (3) LC discounted details
    (4) LC payment due date to our company Bank - as Procurement needs
    to inform to Finance for this.
    Any help will be highly appreciated.
    Thanks and Best Regards,

  • Purchase order to payment

    my client requirement is status of the po till payment i want to generate a sap query any body pls guide me purchase order ->down payment ->goods reciept-> invoice verification -> vendor payment
    i want to generate this report vendor wise as well as the material and po
    pls give me indetails tables and fields
    advance thanks for kind reply

    hi,
    Seelct EKBE u2013 EBELN, LIFNR
    Where EKEB- BUKRS Eq (Company Code entered in the selection screen)
               EKBE u2013 BEDAT Eq (Purchasing Document Date entered in the selection screen)
    Select all EKBE u2013 EBELN  in to EKBE 
    Invoice and GRN Document Number: - 
             Select EKEB-BELNR, BUDAT, DMBTR, WRBTR, WAERS
                         Where  EKBE u2013 EBELN   Eq  EBELN Entered in the selection screen
                                     EKBE u2013 GJAHR Eq  GJAHR Entered in the selection screen
                                     EKBE u2013 BUDAT  Eq  BUDAT Entered in the selection screen
                           EKBE u2013 VGABE  Eq  1 (Goods Receipt) (in case of Invoice GRN)
                                     EKBE u2013 VGABE  Eq  2 (Invoice Receipt) (in case of Invoice MIRO)
             Eenter all EKBE u2013 BELNR into BKPF and select BKPF- BELENR, WAERS
                                    BKPF - BUKRS Eq  BUKRS Entered in the selection screen
                                    BKPF u2013 GJAHR Eq  EKBE - GJAHR
                                    BKPF u2013 BUDAT  Eq EKBE - BUDAT 
                                    BKPF u2013 AWKEY Eq  EKBE u2013 BELNR + GJAHR
             Eenter all BKPF u2013 BELNR into BSEG and select BSEG u2013 BELENR, DMBTR
                                   BSEG - BUKRS   Eq  BKPF - BUKRS 
                                   BSEG u2013 GJAHR  Eq  BKPF - GJAHR
                                   BSEG u2013 BUDAT  Eq  EKBE - BUDAT 
                                   BSEG- BELNR    Eq  BKPF u2013 BELNR
    For Payment Document  Select  BSEG u2013 AUGBL
                                     Where BSEG- BELNR    Eq  BKPF u2013 BELNR
                                                BSEG - BUKRS   Eq  BKPF - BUKRS 
                                                BSEG u2013 GJAHR  Eq  BKPF - GJAHR
                                                BSEG u2013 BUDAT  Eq  EKBE - BUDAT 
    Eenter all BSEG u2013 AUGBL into BSEG and select BSEG u2013 BELENR, DMBTR ,
    Where BSEG u2013 BELNR Eq BSEG - BSEG u2013 AUGBL
    For Advance Payment Document  Select  BKPF u2013 BELNR, WAERS and KURSF
                         Where BKPF - BUKRS Eq  BUKRS Entered in the selection screen
                                    BKPF u2013 GJAHR Eq  EKBE - GJAHR
                                    BKPF u2013 BUDAT Eq EKBE - BUDAT 
                                    BKPF u2013 TCODE Eq FBA7 and FBA6
    Enter all BKPF u2013 BELNR into BSEG and select BSEG u2013 BELENR, DMBTR ,
                                     Where BSEG- BELNR    Eq BKPF u2013 BELNR
                                                BSEG - BUKRS   Eq BKPF - BUKRS 
                                                BSEG u2013 GJAHR Eq  BKPF - GJAHR
    Reagrds,
    Rama Mohan

  • Purchase order and message details

    Hi gurus,
    We have a requirement of generating a report of how the purchase orders are being sent to vendor.
    Is there any table or tables that stores information of a purchase order number and how the message (output type) has been processed to vendor like through what medium it has been sent to vendor.
    Example Purchase order 3456 was sent to vendor through fax.
                   Purchase order 4563 was sent to vendor through paper.
                  Purchase order 7865 was sent to vendor through EDI.
    The transmission medium by which it has been sent to vendor need to be captured by purchasing document.
    So gurus, if anyone can advise me of table or relating tables that i can write a query or request abapers to write a custom report, that would be great.
    Thanks in advance,
    Kind regards,
    Gopio.

    Hi,
    All the CONDITION RECORD details like MESSAGE, DESPATCH TIME & LANGUAGE are available in NACH table
    Goto SE16  for NACH and enter the DOCUMENT CONDITION and get te details
    hope it is helpful
    thanks,
    santosh

  • Purchase Order Report

    When Iam trying to take Purchase Order report,
    Fields in PO Report are as follows:
    Posting date, Purchase Order number,Vendor Name, Item Name, Qty, Unit Price, Total Price, & Status.
    For eg:
    PO Num 100 contains 5 Items, Out of which Goods Receipt PO has been raised for 3 Items. and Goods Receipt PO for remaining 2 items have not been raised.
    In this case PO status is OPEN.
    When iam generating PO Report, It shows Status for all the Items are OPEN. bcoz status for the PO is OPEN.
    I want the report to show the status is Closed for the Items for which Goods Receipt PO has been raised. and similarly status must be OPEN for the items for which Goods Receipt PO has not raised. ( PO number is same ).
    Your answers will be very helpfull.
    Thankyou.

    Hi,
           I have created a Column in Purchase Order Screen and i have given two options by name Open/Close.
    I have Created new field by going into......................      Path: ToolsUserdefined FieldsManage User defined fieldsmarketing documentsrows.
    And i have selected check box  set valid values for fields  and i have given Open and Close Options.
    This is effecting in new Purchase Orders which iam creating from now. But it is not reflecting in Purchase docs which i have created earlier.
    So Please let me know what to be done inorder to reflect this change in all Purchase Order Doc's.
    Your Answers will be very much helpfull.
    Thankyou.

  • Open Purchase Order UPload Using the BAPI 's

    i need to upload the open Purchase Order using the BAPI function BAPI_PO_CREATE1., below is the given fileds blod are for Header, header will Repeat for the line items,can any one help me out  using the BAIP's for upload the PO, i need sample code for this ........
    Thanks & Regards
    Raghu
    <u>Field Name     Field Description                              Type     Length</u>
    <b>EBELN             Purchasing Document Number                         CHAR     010          X
    BUKRS             Company Code                                                     CHAR    004     MN10     C
    EKORG             Purchasing Organization                              CHAR     004     MN00     C
    EKGRP             Purchasing group                              CHAR     003          X
    BSART             Order type (Purchasing)                              CHAR     004          X
    LIFNR             Account Number of Vendor or Creditor                    CHAR     010          X
    BEDAT             Purchase Order Date                              DATS     010          X
    ZTERM             Terms of payment key                              CHAR     004          X
    WAERS             Currency Key                                   CUKY     005          X
    INCO1             Incoterms (part 1)                              CHAR     003          X
    INCO2             Incoterms (part 2)                              CHAR     028          X</b>
    EBELP             Item Number of Purchasing Document                    NUMC     005          X
    EMATN             Material number                                   CHAR     018          X
    WERKS             Plant                                        CHAR     004          X
    LGORT             Storage location                              CHAR     004          X
    EPSTP             Item category in purchasing document                    CHAR     001          X
    KNTTP             Account assignment category                         CHAR     001          X
    EINDT             Item delivery date                              DATS     010          X
    MENGE            "Purchase order quantity (direct input, transfer of POs)"     CHAR     013          X
    MEINS            Order unit                                   UNIT     003          X
    NETPR            "Net price: Document currency (direct input, transfer of"     CHAR     011          X
    PEINH            "Price unit (direct input, transfer of POs)"               CHAR     005          X
    BPRME            Order Price Unit (Purchasing)                         UNIT     003          X
    BPUMZ            Numerator: Conversion OPUn into OUn (direct input of POs          CHAR     005          X
    BPUMN            Denominator: Conversion OPUn into OUn (direct input of P          CHAR     005          X
    SAKTO            Cost element                                   CHAR     010          X
    KOSTL              Cost Center                                   CHAR     010          X
    VBELN          Sales and Distribution Document Number                    CHAR     010          X
    VBELP          Sales document item                              NUMC     006          X
    WEMPF          Goods recipient                                   CHAR     012          X
    WEBTH          "Amount in local currency (direct input, transfer of POs)"     CHAR     013          X
    WEBTF          "Amount in document currency (direct input, transfer of P"     CHAR     013          X
    WEREF          Flag for treatment of GR/IR (direct input of POs)          CHAR     001          X
    SPINF          Indicator: Update info record                         CHAR     001          X
    WEPOS          Goods Receipt Indicator                              CHAR     001          X
    REPOS          Invoice receipt indicator                         CHAR     001          X

    i need to upload the open Purchase Order using the BAPI function BAPI_PO_CREATE1., below is the given fileds blod are for Header, header will Repeat for the line items,can any one help me out  using the BAIP's for upload the PO, i need sample code for this ........
    Thanks & Regards
    Raghu
    <u>Field Name     Field Description                              Type     Length</u>
    <b>EBELN             Purchasing Document Number                         CHAR     010          X
    BUKRS             Company Code                                                     CHAR    004     MN10     C
    EKORG             Purchasing Organization                              CHAR     004     MN00     C
    EKGRP             Purchasing group                              CHAR     003          X
    BSART             Order type (Purchasing)                              CHAR     004          X
    LIFNR             Account Number of Vendor or Creditor                    CHAR     010          X
    BEDAT             Purchase Order Date                              DATS     010          X
    ZTERM             Terms of payment key                              CHAR     004          X
    WAERS             Currency Key                                   CUKY     005          X
    INCO1             Incoterms (part 1)                              CHAR     003          X
    INCO2             Incoterms (part 2)                              CHAR     028          X</b>
    EBELP             Item Number of Purchasing Document                    NUMC     005          X
    EMATN             Material number                                   CHAR     018          X
    WERKS             Plant                                        CHAR     004          X
    LGORT             Storage location                              CHAR     004          X
    EPSTP             Item category in purchasing document                    CHAR     001          X
    KNTTP             Account assignment category                         CHAR     001          X
    EINDT             Item delivery date                              DATS     010          X
    MENGE            "Purchase order quantity (direct input, transfer of POs)"     CHAR     013          X
    MEINS            Order unit                                   UNIT     003          X
    NETPR            "Net price: Document currency (direct input, transfer of"     CHAR     011          X
    PEINH            "Price unit (direct input, transfer of POs)"               CHAR     005          X
    BPRME            Order Price Unit (Purchasing)                         UNIT     003          X
    BPUMZ            Numerator: Conversion OPUn into OUn (direct input of POs          CHAR     005          X
    BPUMN            Denominator: Conversion OPUn into OUn (direct input of P          CHAR     005          X
    SAKTO            Cost element                                   CHAR     010          X
    KOSTL              Cost Center                                   CHAR     010          X
    VBELN          Sales and Distribution Document Number                    CHAR     010          X
    VBELP          Sales document item                              NUMC     006          X
    WEMPF          Goods recipient                                   CHAR     012          X
    WEBTH          "Amount in local currency (direct input, transfer of POs)"     CHAR     013          X
    WEBTF          "Amount in document currency (direct input, transfer of P"     CHAR     013          X
    WEREF          Flag for treatment of GR/IR (direct input of POs)          CHAR     001          X
    SPINF          Indicator: Update info record                         CHAR     001          X
    WEPOS          Goods Receipt Indicator                              CHAR     001          X
    REPOS          Invoice receipt indicator                         CHAR     001          X

  • OPEN PURCHASE ORDER

    DEAR ALL,
    WHETHER WE HAVE A STANDARD REPORT IN SAP TO GET QUANTITY AND VALUE DATA OF BACK DATED OPEN PURCHASE ORDER?
    PURCHASE ORDER HAS BEEN PREPARED IN JANUARY, DOWN PAYMENT IS MADE IN THE MONTH OF MARCH, MATERIAL IS RECEIVED (GRN MADE) IN AUGUST
    IN ABOVE CASE WHEN I GENERATE A OPEN PURCHASE ORDER REPORT AS ON 31.03.2008 IT IS NOT SHOWING ME THE QUANTITY & VALUE DETAILS OF OPEN PURCHASE ORDERS.
    PLEASE LET ME KNOW THE WORK AROUND.
    WAITING
    AMIT

    Dear,
    Enter ME2N, Select WE101 in selection parameter field.
    Then enter other required detail and click on execute button.
    So system give you list of open purchase order.
    Then click on change layout button.
    Transfer Still to be invoiced (qty) field Column Set to Display column set mode.
    And click on continua button.
    Duse to this field you can track for how many quantity good receipt is created of purchase order.
    Regards,
    Mahesh Wagh

  • Purchase order to payment cycle report

    Dear Sir/Madam
    We want to have a report on the purchase order to payment cycle.
    this includes the following points:
    1. Purchase Requisition is raised in the system
    2. PO is raised with various line items
    3. Advance payment is done against the PO
    4. GRN is made for goods delivered
    5. Invoice is processed against each GRN
    6. Retention is deducted to be paid in future
    7. Liquidated damages (LD) is deducted which is treated as miscellaneous income in companys books
    8. Payment is made to the vendor
    We require the report in such a way which will give the details of each payment against each GRN line item. tracking of the same should be possible.
    Do we have any standard report which will help in identifying the purchase order to payment cycle.
    Thanks and Regards
    Prashant P. Zinge

    Hi,
    It is always a requiremnet to have a report from PO, GR, IV to payment.
    But unfortunately, SAP do not have such a report, we develop one locally, the difficult is at payment side.
    Several invoices for one vendor has only one payment doc, how to display it need to discuss with end user.

  • Purchase order status open

    Hi Experts,
    Due to some other reasons we tried clear GR/IR clearing a/c. i will explain clearly.
    We have some purchase orders pertaining to 2006 year. we have not done MIGO and we did MIRO, So that we could not able to clear GR/IR A/C. SO, we have posted manual entry with fb50 same as MIGO posting then we cleared both documents with f-03 its done every thing was fine now But if we see purchase order report status showing OPEN
    How to change the status please some one let me know.this is high priority issue.
    Regards,
    JC

    Hi,
    First make sure that you will not receive goods against your PO..Then go to me22n and delete the item in your PO.
    This will resolve your issue.
    Thanks,
    Srinu

  • Report for Planned vs Purchase Order(Qty and rate)

    Hi
    I have the following issue. My client is raising Purchasing requisition and Purchase Orders in Me51N and ME21n respectively. The Project Structure is used only to plan the quantities and rates whereas no PR is released from it. But the components are attached. Now if i make use of the code CN52N, i am getting the planned quantity and unit rate for the planned value whereas no Purchase requisition number or purchase order number is updated in it.
    My requirement is that both planned quantity, rate along with Purchase order quantity and rate should be available in a report.
    1. Is there any setting that we can make so that the details are updated in cn52N (or)
    2. is there any other report with those details (or)
    3. Should that be achived only through ABAP.
    Please suggest.
    Raghav

    There are a few reports that you can use to display STO requisitions and orders, by supplying plant, material, or MD04 like was mentioned.
    The only thing that you don't have in a report is the link to the production order. In SAP in a MTS situation there's no fixed link (pegging) between the requirement (STO) and the supply (prod Ord).
    You can view the pegging dynamically, for example in MD04.
    Edited by: Mario Adler on Oct 27, 2011 12:13 PM

Maybe you are looking for

  • STRANGE: single clip missing in export! (but still in the timeline)

    Strangest thing: I exported a project... and a SINGLE clip is missing. BUT... the "key" over that clip shows up (over "black.") Hmmm... So I went back to the timeline... the clip is STILL THERE! So, I re-rendered, exported again... SAME THING. That o

  • How do I connect my mac book pro to a wireless LCD

    I want to connect my Macbook Pro to a wireless LCD projector. I am not sure how to do it. Do I need to download software? Do I have the hardware I need?

  • Discoverer Desktop Report issue

    Hi, One of my user is facing a format issue while running the report in Oracle Discoverer 10g. The report produces the following out put. count(Col A)     Col B     Col C     Col D 12          A     200709     12-Sep-07 11          A     200709     2

  • Pdf will not open when created

    A recent problem has popped up.  When creating a new pdf document the save as window stays in the task bar until I click on it.  Once the pdf is created it stays in task bar until I click on it to view on it.  Using windows 7 and Adobe Pro 9 Extened.

  • RG1 Issue

    Dear All while doing J1I5 I am getting like this Thanks Kumar