Line item status of the PO

Hi All,
Could you please let me know once PO line item is deleted in which table this information will be stored.
Appreciate early action

HI,
PO line item deleted information stored in EKPO table and the line item deletion indicator 'L' stored in LOEKZ field name.
LOEKZ field name description means  'Deletion indicator in Purchasing Document'.
Hope, it is useful for you.
Regards,
K.Rajendran

Similar Messages

  • Change line item status at table level & also in transaction.

    Hello,
        I want to change the status of line item in CRM service order at table level. This change should reflect in transaction too.
    Ex. Order X is in release state. When i run my program for line item 10 with enabling a check box in the selection screen, then the line item status shd be changed to "complete".
    Table to change status is CRM_JCDS. Kindly send sample code on how to change the status in order through pgm.
    Regards
    Devika.S

    Hi Nikhil
    Open item management tick checked in GL master as we have run the program FAGL_SWITCH_TO_OPEN_ITEM .
    Also GL shows the line item dispaly as RFSEPA01 had been executed.
    However FAGLL03 shows all the old line item as posted status -we are looking for option have the status of all the old
    line item as open item indicatior(in red) there by we can have the option to select all the item to process open item in F-03.
    Appreciate for an amicable solution on this.
    Regards
    subrata

  • How to add the line items while running the VA01

    HI All,
    I want to add the line items while I am running the VA01 t-code(In run time).Could anybody give the FM to create the line items....Its urgent

    Hi ,
    User Exits In Sales Document Processing
    This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
    Involved program components
    System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
    MV45ATZZ
    For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
    MV45AOZZ
    For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
    MV45AIZZ
    For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
    MV45AFZZ and MV45EFZ1
    For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
    User exits in the program MV45AFZZ
    The user exits which you can use for modifications in sales document processing are listed below.
    USEREXIT_DELETE_DOCUMENT
    This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
    For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
    The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
    USEREXIT_FIELD_MODIFICATION
    This user exit can be used to modify the attributes of the screen fields.
    To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
    The usage of the field groups (modification group 1-4) is as follows:
    Modification group 1: Automatic modification with transaction MFAW
    Modification group 2: It contains 'LOO' for step loop fields
    Modification group 3: For modifications which depend on check tables or on other fixed information
    Modification group 4: is not used
    The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
    This FORM routine is called up by the module FELDAUSWAHL.
    See the Screen Painter manual for further information on structuring the interface.
    USEREXIT_MOVE_FIELD_TO_VBAK
    Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBAP
    Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBEP
    Use this user exit to assign values to new fields at the level of the sales document schedule lines.
    The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBKD
    Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
    The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
    USEREXIT_NUMBER_RANGE
    Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
    The user exit is called up in the FORM routine BELEG_SICHERN.
    USEREXIT_PRICING_PREPARE_TKOMK
    Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
    USEREXIT_PRICING_PREPARE_TKOMP
    Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
    USEREXIT_READ_DOCUMENT
    You use this user exit if further additional tables are to be read when importing TA01 or TA02.
    The user exit is called up at the end of the FORM routine BELEG_LESEN.
    USEREXIT_SAVE_DOCUMENT
    Use this user exit to fill user-specific statistics update tables.
    The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
    Note
    If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
    USEREXIT_SAVE_DOCUMENT_PREPARE
    Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
    The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
    User exits in the program MV45AFZA
    USEREXIT_MOVE_FIELD_TO_KOMKD
    Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMPD
    Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMKG
    Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_MOVE_FIELD_TO_KOMPG
    Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_REFRESH_DOCUMENT
    With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
    For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
    The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
    The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
    User-Exits in program MV45AFZB
    USEREXIT_CHECK_XVBAP_FOR_DELET
    In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
    USEREXIT_CHECK_XVBEP_FOR_DELET
    In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
    USEREXIT_CHECK_VBAK
    This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
    USEREXIT_CHECK_VBAP
    This user exit can be used to carry out additional checks (e.g. for completion) at item level.
    USEREXIT_CHECK_VBKD
    The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
    USEREXIT_CHECK_VBEP
    This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
    USEREXIT_CHECK_VBSN
    You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
    USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
    USEREXIT_FILL_VBAP_FROM_HVBAP
    You can use this user exit to fill additional fields in the sub-item with data from the main item.
    USEREXIT_MOVE_FIELD_TO_TVCOM_H
    You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    USEREXIT_MOVE_FIELD_TO_TVCOM_I
    You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    User-Exits for product allocation:
    The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
    USEREXIT_MOVE_FIELD_TO_COBL
    Option to include new fields in structure COBL.
    USEREXIT_COBL_RECEIVE_VBAK
    Option to assign values from the document header to the new fields.
    USEREXIT_COBL_RECEIVE_VBAP
    Option to supply values from the item to the new fields.
    USEREXIT_COBL_SEND_ITEM
    A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
    USEREXIT_COBL_SEND_HEADER
    A changed field can be copied from the structure to the header (see source text MV45AFZB)
    USEREXIT_SOURCE_DETERMINATION
    You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
    USEREXIT_MOVE_FIELD_TO_ME_REQ
    With this user exit you can include additional fields for the following fields:
    EBAN (purchase requisition)
    EBKN (purchase requisition-account assignment)
    USEREXIT_GET_FIELD_FROM_SDCOM
    Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
    USEREXIT_MOVE_WORKAREA_TO_SDWA
    You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
    User-Exits for first data transfer:
    The following user exits can only be used for the first data transfer.
    Note
    Only use the user exits if the names/fields do NOT have the same name.
    USEREXIT_MOVE_FIELD_TO_VBAKKOM
    Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
    USEREXIT_MOVE_FIELD_TO_VBAPKOM
    Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
    USEREXIT_MOVE_FIELD_TO_VBEPKOM
    Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
    USEREXIT_MOVE_FIELD_TO_VBSN
    You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
    USEREXIT_MOVE_FIELD_TO_KOMKH
    You can use this user exit to include new fields for batch determination (document header).
    USEREXIT_MOVE_FIELD_TO_KOMPH
    You can use this user exit to include new fields for batch determination (document item).
    USEREXIT_CUST_MATERIAL_READ
    You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
    USEREXIT_NEW_PRICING_VBAP
    Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
    USEREXIT_NEW_PRICING_VBKD
    Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
    User-Exits in Program MV45AFZD
    USEREXIT_CONFIG_DATE_EXPLOSION
    The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
    User exits in the program FV45EFZ1
    USEREXIT_CHANGE_SALES_ORDER
    In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
    If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
    User-Exits in Program RV45PFZA
    USEREXIT_SET_STATUS_VBUK
    In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
    The following workareas are available for this user exit:
    VBUK (header status)
    FXVBUP (item status)
    FXVBUV (Incompletion)
    USEREXIT_SET_STATUS_VBUP
    In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
    The following workareas are available for this user exit:
    FXVBAP (Item data)
    FXVBAPF (Dynamic part of order item flow)
    FXVBUV (Incompletion)
    USEREXIT_STATUS_VBUK_INVOICE
    You can use this user exit to influence billing status at header level.
    User exits in the screens
    Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
    Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
    For field transports, you do not have to make changes or adjustments.
    Example
    A new field, VBAK-ZZKUN, should be included in table VBAK.
    If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
    User Exits in Program MV45AFZ4
    USEREXIT_MOVE_FIELD_TO_KOMK
    You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
    USEREXIT_MOVE_FIELD_TO_KOMP
    You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
    User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
    EXIT_SAPFV45P_001
    You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
    regards
    P.

  • Order Line Item Status Issue

    Experts,
    The way that order line item status is determined in SAP is causing confusion with our customers how are using our ECommerce for ERP module.  The line item status does not take into account the line item's delivery statuses.  For example, a line can be complete in SAP, even through its delivery is partial.  From a customer's standpoint, the line item is not complete until all the deliveries are complete.
    I would love to hear how are other companies are addressing this issue?  Do they enhance the ECommerce module, or ECC?

    Check the [Modification Guide|https://websmp210.sap-ag.de/~sapdownload/011000358700000469462006E/]"  for the tip. See the section on Replacing calls to standard function modules.
    Register the function module within WEB-INF/xcm/customer/modification/modficationconfig.xml
    <function-module-replacement>
    <param name=u2018fm:CRM_ISA_SHOP_GETLISTu2019 value=u2018Z_CRM_ISA_SHOP_GETLISTu2019/>
    </function-module-replacement>
    Instead of the standard function module, your function module will be called during runtime.
    Easwar Ram
    http://www.parxlns.com

  • FI line items up to the current date

    Hi all,
    I read the SAP note 485958 "BCT-FI:Extracting FI line items up to the current date" and I have some doubts here:
    1. After I've set parameter BWFIOVERLA to 'X' and extract delta at 6PM, will FI data that is changed before 6PM for example a gl entry at 5PM, goes into my delta extraction?
    2. What does BWFITIMBOR mean by having default value 02:00:00?
    3. Is this note applicable if my R3 PI release is at 2003_1_46C?
    Please advise.
    Thank you.
    Celeste

    Hi Celeste,
       Pls go through this link:
    http://help.sap.com/saphelp_nw04/helpdata/en/af/16533bbb15b762e10000000a114084/content.htm
    Excerpts from this link regarding your doubt:
    BWFIOVERLA: The logic of this parameter prevents records with the previous day as their CPU date from still being in the update at the time of extraction.
    If X is set for this parameter, selection is made up to the previous day if the time limit is not reached.
    If <space> is set for this parameter, selection is made up to the day before the previous day if the time limit is not reached.
    BWFITIMBOR: This parameter designates 02.00 (2 A.M.) as the time limit for extraction. If this limit is not reached, the system uses a security interval of one day to determine the To-value of the selection. If extraction is started before 02:00 therefore, the selection takes place only up to the day before the extraction run.
    Hope it helps you!!!!
    Regards,
    Amit

  • How to make plant default on the line item along with the item category

    Hi All,
    I want to default Plant on the line item along with the item category.In order to meet the following scnario.
    1. I have two plants,first plant is maintained for the valuated item and the second plant is maintained for the non valuated item (Free Goods).
    Whenever user is entering an item in the sales order for which corresponding free goods item is maintained in the master record.System is proposing two lines items in the sales order.
    First line item is the main item which appears along with the Plant 1 which contains valuated items
    Second line item is for the Free of charge item which is being proposed from Plant 2, which contains the non valuated items.
    I want that the system should always propose Plant 1 with main item and Plant 2 with the Free of Charge item by default. (Along with the item category TAN and TANN)
    Rahul

    Delivering Plant is determined in the following order
    1. Customer material info record.
    2. Customer master
    3. Material master.
    Use one of them an default your plant.
    I think in your case you can use the materila master which will give an item level plant different. The other two will default the plant at the header level.
    regards
    jude

  • How to add the line item text in the Ledger line item report

    Hi SAP Gurus,
    I having one requirement from the user. He wants the line item text which we will enter in FB60/FB70/FB50 has to be shown in the Ledger line item report. Right now this field is not available. Is there any possible we can make this line item text in the ledger line item report i.e. FBL1N/FBL3N/FBL5N?
    advance thanks for the help.
    Regards,
    Deva.

    Hi,
    You can do the below to get this. (You can change the names of the function modules as per your wish/ organization naming convention):-
    Step 1:-
    Create function module Z_GET_SGTXT as below:-
    Import:-
    BELNR LIKE BKPF-BELNR
    BUKRS LIKE BKPF-BUKRS
    BUZEI LIKE BSEG-BUZEI
    GJAHR LIKE BKPF-GJAHR
    Export:-
    PRCTR LIKE BSEG-SGTXT
    FUNCTION Z_GET_SGTXT.
    ""Local Interface:
    *" IMPORTING
    *" VALUE(BELNR) LIKE BKPF-BELNR
    *" VALUE(BUKRS) LIKE BKPF-BUKRS
    *" VALUE(BUZEI) LIKE BSEG-BUZEI
    *" VALUE(GJAHR) LIKE BKPF-GJAHR
    *" EXPORTING
    *" VALUE(SGTXT) LIKE BSEG-SGTXT
    SELECT SINGLE SGTXT FROM BSEG INTO SGTXT WHERE GJAHR = GJAHR
    AND BELNR = BELNR
    AND BUKRS = BUKRS
    AND BUZEI = BUZEI.
    ENDFUNCTION.
    Step 2:-
    Then create the Function Modules as below:-
    Z_LINE_ITEMS_GET_SGTXT (Copy of SAMPLE_INTERFACE_00001650)
    FUNCTION Module Z_LINE_ITEMS_GET_SGTXT.
    ""Local Interface:
    *" IMPORTING
    *" VALUE(I_POSTAB) LIKE RFPOS STRUCTURE RFPOS
    *" EXPORTING
    *" VALUE(E_POSTAB) LIKE RFPOS STRUCTURE RFPOS
    Initialize Output by using the following line
    E_POSTAB = I_POSTAB.
    E_POSTAB = I_POSTAB. "<-- important
    CALL FUNCTION 'Z_GET_SGTXT'
    EXPORTING
    BELNR = I_POSTAB-BELNR
    BUKRS = I_POSTAB-BUKRS
    BUZEI = I_POSTAB-BUZEI
    GJAHR = I_POSTAB-GJAHR
    IMPORTING
    SGTXT = E_POSTAB-SGTXT
    EXCEPTIONS
    OTHERS = 1.
    ENDFUNCTION.
    Step3:-
    Transaction FIBF:-
    Settings -> Products -> of a Customer
    SGTXT Text in Line Item Display Active
    Settings -> P/S Module -> of a Customer
    00001650 SGTXT Z_LINE_ITEMS_GET_SGTXT
    Step 4:-
    Create the layout for FBL*N with display of the TEXT.
    Regards,
    Gaurav

  • A List of Customer Line Items according to the *CONTACT PERSON*

    Hi All,
    I'm looking for a report which shows the  List of Customer Line Items according to the CONTACT PERSON data, that I can find in the customer master data.
    Thanks for your help

    Not sure if you can add this field to the selection criteria. Please look at OSS notes 188663, 310886. I remember there were some restrictions as only fields from certain tables are allowed to use in FBL1N, FBL3N and FBL5N transactions.
    Shail

  • Can we able to see the Work Items status in the BPM Workspace

    HI,
    Can we able to see the work item status in the BPM workspace.
    For exampls, I have create the request as requester then it will go for approval.
    After sometime i login into the workspace can i able to see my request status(it mean where it is like approval1, approval 2)?
    Pls let me know, its possible in the BPM workspace.
    Regards,
    Anandh P

    Hello Anandh,
    You can utilse the filter option of the BPM workspace.
    When you filter the instances you can view the status of all the instances even if they are currently not assigned to the particular user.
    All you need to do is click on the show filter link.
    Select the process from the Filter by: combo box.
    Check the status boxes and click on apply filter.
    You will be able to view the instance even if it is not assigned to you.(Though you will not be able to work on it.)
    If you wish to give custom messages like "pending with HR" or "Pending with Admin" then you need to add a column by creating a project variable and mapping it to the custom view. Then these messages can also be shown on the instances.
    Hope ths helps.
    Regards,
    Jaydev Doshi

  • How to pass line item values in the table paramer of FM

    Hi all,
    When i will give the import of  the FM as VBELN"sales order number.
    I want to display all the line items for "PO Quantity in the out put of the FM.
    For this i thnk i have to pass the line item values in the table parameter of the FM.
    Can any body please tell me how to pass the values for the line items in the table parameter fo teh FM.
    Please give a example.
    Thanks

    Sub pLoopThroughPivotFields()
    Dim oItem As Excel.PivotItem
    Dim oField As Excel.PivotField
    Set oField = ThisWorkbook.Worksheets("Sheet1").PivotTables("Pivot Table name").PivotFields("field name")
    For Each oItem In oField.PivotItems
    oField.CurrentPage = oItem.Name
    'Put your copy code here
    DoEvents
    Next oItem
    End Sub
    Felipe Costa Gualberto - http://www.ambienteoffice.com.br

  • SO line item status field ASTTX

    Hi,
    I need Sales Order line item status filed (ASTTX) in which table it will store.
    Regards
    Ajay ilavaram

    Did you check out tables JEST and JSTO.

  • Sales Order Line item status with Resource Related Billing

    Hi
    The Resource related billing is done based on the costs accumulated on account assigned WBS Element. The WBS Element system status is set 'Finally Billed'. The overall status of Sales Order line item is still 'open' and does show up in 'Open Order' reports.
    SAP vide their note 439288 recommends running report SDVBUK00 to correct the sales Order item status. However this note is applicable only upto 4.6C. Our system in ECC 6.0. We tried running this report and did not get desired results. We checked the program and discovered that the corrections suggested as per above note, are not available.
    Is there any new SAP note applicable for ECC 6.0 needs to be applied ? Or is there any other report needs to be run in case of ECC6.0?
    Thanks in advance
    with regards

    HI,
    Please raise message to SAP through service marketplace.
    Thanks,
    Vrajesh

  • Sales order line item status for an item with PR

    Hi Gurus,
                  Here is my business scenario.
    i have got following list of line items in a sales order.
            Line item no        Material no       Order quantity     Schedule line confirmed qty     Line item overall status           Plant
                    10        A                    3                              3                                   Open                         X
                    20        B                    5                              5                                    Open                        X
                     30        C                    8                              0                                    Open                        X
    1. I can create delivery for the line tiem 10 & 20 as they are confirmed for schedule lines.
    2. Line item 30 is not actually available in Plant X now if i do the availability check and select another plant "Y" where the material is available. For this STO should process should follow up (Correct me if i am wrong)
    Now i have got following questions
    1. How can i track which line items are followed up by PR's and which are not in the sales order.
    2. tell me how follow up happens by creating PR's
    Thank you

    1. So i am assuming that for each schedule line item there will be associate PR number and PO number if there are any.
    Yes every non stock article will have a associated PO.
    2. Suppose if Purchasing department make a decision to get this line item thru 3rd party then what happens for this schedule line item.I mean how do we differentiate in showing Sales order? Here my scenario is one Material can get thru either STO or thru 3rd Party.
    If you have more than 1 vendor listed for an article in EINA table. Then at that point the system will prompt you to select the vendor you want to create the PO against. (Given that the regular vendor flag is not checked for any vendor).
    Eg: Suppose if i have a schedule line item which can get thru STO and i have got another schedule line item which i can get thru 3rd party, Can i see this differentiation in sales order?
    3. How to create purchase requisition?
    Tcode Me21n (Advise to use this tcode) or ME21
    Found a link hope this helps
    http://www.le.ac.uk/mis/docs/sapdocs/mm/mm46b_41.doc

  • PO line item delete with the customised message type

    Hi,
    My requirement is...In a Multiple line item PO if all the line items are deleted than it should not send any print to the vendor though the message option is set to Print immediatelly(NAST-VSZTP = 4).
    These message type are customised output type like ZNEU.
    I have tried to stop the print program which is calling the smartfrom.I am successful in stopping it by taking the deletion flag from the table ekpo table.But not able to make the traffic signal light to red.Because after the print program it is going to the RSNAST00 program and taking the value NAST-VSZTP = 4 and make its status to green and as well as processed.
    Can any body suggested how to change this traffic signal light to red.
    Regards,
    Partha

    Hi Raghavendra,
                           I understand that you are facing problems due to non-availibility of Header data in PROCESS_ITEM. But the same can be pulled live from the program. Sample pseudo code and reference link provided below. Hope it helps your ABAPer gain an insight.
    REF: Getting Header Data in ITEM_PROCESS
    DATA: ls_item TYPE mepoitem,
    ls_header TYPE mepoheader,
    ls_header_obj TYPE REF TO if_purchase_order_mm.
    *Get PO Header data
    CALL METHOD im_item->get_header
    RECEIVING
    re_header = ls_header_obj.
    CALL METHOD ls_header_obj->get_data
    RECEIVING
    re_data = ls_header.

  • CRM line item status not updated when delivery is deleted in ECC

    Hi All,
    When order is created in CRM it gets replicated to ECC.When delivery is created in ECC, the System Status in CRM  at the line item level is changed to completed and also Delivery completed status is created in CRm..
    Now when we delete the delivery, the Delivery completed status is deleted in CRM but the Completed status is not changed to In Process.It remains as Completed.This used to work fine before we applied support packs last weekend.We are currently at support pack level 10 for CRM.
    Please advice
    Thanks and Regards

    In CRM4 standard, changes to orders in R/3 or ECC do not replicate back to CRM
    Check out this SAPnote
    https://service.sap.com/sap/support/notes/710874

Maybe you are looking for