Check Vendor no. in CRMD_ORDER on order_save

Hello,
I have requirement in which i have to check if in the CRMD_ORDER a vendor exist for a sales org extended to a BP...
If the Vendor does not exist i have to put a hard break on save(order_save).
Can anyone please suggest how do i check if the vendor no exist in the CRMD_ORDER on creation before save..
I tried a few internal tables from CRMD_ORDER_READ but none so helpful.
Please advice!
Thanks in anticipation!!
Alok.

Hi Alok,
Since a Vendor is a business partner it will be present in ET_PARTNER internal table of the CRM_ORDER_READ Function Module. So, you can scan the internal table to get whether a BP with the Role VENDOR is present in the One Order Transaction.
Have a look at the existing code and you can also use the Report Program CRM_ORDER_READ to have a look at all the data that will come in the various internal Tables.
Hope this will help.
Thanks,
Samantak.

Similar Messages

  • How to check vendor payment

    Hi gurus,
    how to check vendor payment is done are not in purchase order
    Regards
    murali

    Check through FBL1N vendor line item display, here you can check for the vendor libality generated during invoice (MIRO) posting once you get into the t-code FBL1N select the radio button open items only in line item selection give your vendor account, company code date (Key day at which the line items are open till now), and execute.
    In the report screen to help your self you can search using crtl + F and put reference as serach criteria.
    You will see the non cleared item the Status indicator tells you the line item is not yet cleared.
    BR

  • Reg:How to check Vendor for particular Asset

    HI
    How to check Vendor for particular Asset?
    regards
    JK rao

    Hi,
    Good morning and greetings,
    It would be very difficult to go into each and every asset and display the asset...instead create a quick viewer query using SQVI and use the table ANLA and the field name is LIFNR for Vendor Code and for Asset Number it is ANLN1.
    Please reward points if found useful
    Thanking you
    With kindest regards
    Ramesh Padmanabhan

  • How to check vendor schema group for info record for third party vendor

    Hi Expert,
    How to check vendor schema group that assigned in info record for third party vendor?
    Thanks

    Hi,
    Vendor schema group is not assigned in info record, It is assigned in purchasing data view of vendor master ( Check in XK03 )
    You can check in Vendor master- XK03- Purchasing data.
    hope it will help u.
    Deepak

  • Match Codes / Search Helps for Duplicate Check Vendor are missing

    Hi Guys,
    I'm trying to enable the Duplicate Check for the Vendor solution we have here and I couldn't help, but notice that when I'm setting up the DB Search in "Define Search Application", the out of the box values for existing search helps are already preconfigured and the values are the following:
    BP MC_BP_ADDRESS Address Data
    BP MC_BP_BANK_DETAIL Bank Details
    BP MC_BP_GENERAL General Data
    BP MC_BP_ID_NUMBER Identification Numbers
    BP MC_BP_ROLES BP Roles
    Unfortunately, when I check in SE11 - those search helps do not exist in the system. How can I get them deployed? Are they part of a Business Set that I missed to install and activate?
    Thanks in advance,
    Boris

    Hi Boris
    Please check that the following is set in your system:
    Configure Duplicate check for entity types - BP need the following:
    Assign search object connector template to object types - BP need the following:
    Ensure that "Business Partner template for MDG" connector is created in ESH_COCKPIT
    Regards
    Danie

  • Duplicate Invoice Check -Vendor

    Hi everyone,
    I found  out that I posted an invoice(FB60) for the same vendor with same, amount, reference,invoice date,same company code.one invoice was posted on 3rd march and  other was posted on 25th march,I checked in the vendor master record indicator" chk double inv" is checked.Why system didn't give any error or warning message.Please guide.
    Regards
    Shaun

    Hi,
    Good Day,
    Please follow the below steps ( taken from another post and its working fine for me)
    The following fields must be identical for Duplicate invoice check
    Company code (BUKRS)
    Vendor number (LIFNR)
    Currency (WAERS)
    Reference number (XBLNR)
    Amount in document currency (WRBTR)
    Document date (BLDAT)
    If the document is having any one of the above filed different then the
    system does not consider it as a duplicate invoice.
    and also It will check duplicate invoice check in vendor master data
    and in posting key is there check box selected for sales related
    The setting you making in OMRDC i.e Materials management->Logistics
    Invoice Verification->Incoming Invoice ->Set Check for Duplicate
    Invoices is only valid for MM and not FI invoices posted via FB60/FB65.
    You should check the F1 help on field "Chk double inv." (LFB1-REPRF)
    in the relevant vendor master record (transaction FK03).
    Please also check, that message F5 117 has been set correctly in the
    IMG using this path:
    Financial Accounting -> Financial Accounting Global Settings ->
    Document -> Default Values for Document Processing -> Change Message
    Control for Document Control For Document Processing
    Finally & mainly, go to the relevant posting key is defined as sales
    related in transaction OB41. You have to flag this field if the
    duplicate invoice check should work.
    Best Regards,
    KSK

  • How to check Vendor issue stock shelf life

    Hi,
    As I know, Tcode--MB5M is for checking shelf life for normal stock material.
    The question from our user is to check the batch shelf life which has been transferred from our restrict stock to vendor issue retrict stock. MB5M seems not make it...
    Thanks a lot.
    Bryan

    Hi Pankaj,
    Thanks firstly. But Tcode-MBLB is for checking the stock in subcontracting.
    What I am seeking for is a transaction to check the shelf life of the stock. ( In our system, we use batch management..So the exact question should be that how to check the shelf life of batch which is under subcontracting stock.)
    If you try Tcode-MB5M, you would know this tcode is for checking batch shelf life under normal stock, but it could not used for checking the shelf life of batch under subcontracting.
    Thanks alot.
    Bryan

  • Check Vendor X Purchase Order in VL31N

    Hi all,
    I am currently working on inbound delivery(TCode VL31N) and I need to check that a vendor does not create an Inbound Delivery with a PO that is not yours, that is, he just can select his owns POu2019s . ¿Is that possible? ¿How could I do that? ¿Could someone help me, please?
    Thank you very much and best regards.
    Laiz S. Martins

    Check if the function EHSWA_112_PO_CREATE_V1 calls the function BAPI_PO_CREATE1 or BAPI_PO_CREATE
    If the first function is called, read this note 1111389, check service pack level of your version

  • User exit to check vendor tax type in tcode FB60

    Dear All,
    i need o create an user exit for FB60  check the vendor tax types .
    Plz advice.
    regards
    siva

    Hi,
    check these..
    Enhancement/ Business Add-in            Description
    Enhancement
    SAPLF051                                Workflow for FI (pre-capture, release for payment)
    RFKORIEX                                Automatic correspondence
    RFEPOS00                                Line item display: Checking of selection conditions
    RFAVIS01                                Customer Exit for Changing Payment Advice Segment Text
    FEDI0001                                Function Exits for EDI in FI
    FARC0002                                Additional Checks for Archiving MM Vendor Master Data
    F180A001                                Balance Sheet Adjustment
    F050S001                                FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
    F050S002                                FIDCC1: Change IDoc/do not send
    F050S003                                FIDCC2: Change IDoc/do not send
    F050S004                                FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
    F050S005                                FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document
    F050S006                                FI Outgoing IDoc: Reset Clearing in FI Document
    F050S007                                FIDCCH Outbound: Influence on IDoc for Document Change
    Business Add-in
    FBAS_CIN_MF05AFA0                       EWT - Downpayment Clearing - Tax transfer for CIN
    FISPLIT                                 Online Split: Cash Discount, Exchange Rate Differences
    FI_AUTHORITY_ITEM                       Extended Authorization Check for Document Display (FB03)
    FI_DOC_DISP_LI                          Diversion to Document Items (FB03)
    FI_FB08_SUBST_BUDAT                     FB08: Check Posting Date for Reversal of FI Doc. with FB08
    FI_GET_INV_PYMT_AMT                     BAdI for determining the payment amount for an invoice
    FI_HEADER_SUB_1300                      Screen Enhancement for Document Header SAPMF05A
    FI_PAYREF_BADI_010                      BAdI: Payment Reference Number
    FI_RES_ITEM_CURRENCY                    Document of Residual Item with Invoice Currency
    FI_TRANS_DATE_DERIVE                    Derive BKPF-WWERT from Other Document Header Data
    FVFZ                                    Replacement for Function Modules of Function Group FVFZ
    INVOIC_FI_INBOUND                       BADIs for Inbound IDoc INVOIC FI (Vendor Invoice)
    RFESR000_BADI_001                       BAdI for Own Processing of POR Item
    AC_QUANTITY_GET                         Transfer of Quantities to Accounting - Customer Exit
    ADJUST_NET_DAYS                         Change to Net Due Date
    BADI_ENJ_ALT_ADR                        Go to alternative vendor/customer data
    BADI_F040_SCREEN_600                    Screen Enhancement on F040 0600 Document Header
    BADI_FDCB_SUBBAS01                      Screen Enhancement 1 on FDCB Basic Data Screen (010, 510)
    BADI_FDCB_SUBBAS02                      Screen Enhancement 2 on FDCB Basic Data Screen (010, 510)
    BADI_FDCB_SUBBAS03                      Screen Enhancement 3 on FDCB Basic Data Screen (010, 510)
    BADI_FDCB_SUBBAS04                      Screen Enhancement 4 on FDCB Basic Data Screen (010, 510)
    BADI_FDCB_SUBBAS05                      Screen Enhancement 5 on FDCB Basic Data Screen (010, 510)
    BADI_MIRO_SPLT_ADD                      Append additional fields of ACCVS to ACCIT
    BADI_PRKNG_NO_UPDATE                    BAdI for Deactivating Update of Parked Documents
    F050S008                                FIDCC1, FIDCC2 Inbound IDoc: Update Comparison Ledger
    FBAS_CIN_LTAX1F02                       Tax interface
    No.of Exits:         14
    No.of BADis:         26
    Arunima

  • BAPI Not checking Vendor existance (BAPI_VENDOR_EXISTENCECHECK)

    Hi all.
    My BDC will created and update the vendor. code is
    Check the vendor existance using BAPI_VENDOR_EXISTENCECHECK.
    IF VENDOR exist.
    Update the VENDOR.
    ELSE.
    Create VENDOR.
    ENDIF.
    But the problem is, in case of update record come very next one of the creation of same record.
    For the first record BAPI giving vendor doesn't exist and creating, it is fine but
    For second one BAPI is giving vendor doesn't exist but the same is exist.
    data
    (1000091098 ''''''''' 1st record'
    1000091098 ''''''''''') 2nd record
    I can't use the select statement instead of BAPI.
    Why the BAPI is getting fails to do. i am using commit work after BDC also.
    Regards,
    Sri

    I know it's solved (thank you for the feedback), but...
    > The BAPI is getting from the data and keeping in buffer.so at next time it is checking against buffer values.
    > I copied BAPI into ZBAPI and passing buffer as X.
    As you are talking about a buffer, I thought you might be interested by this [wiki which explains why you MUST use BAPI_TRANSACTION_COMMIT instead of COMMIT WORK|http://wiki.sdn.sap.com/wiki/display/ABAP/BAPI_TRANSACTION_COMMITversusCOMMIT+WORK] when you use BAPIs, and what is this buffer about.
    > i am using commit work after BDC also
    Executing COMMIT WORK after a CALL TRANSACTION will have no effect on what is done inside the CALL TRANSACTION because it's done in a different LUW (see [sap library|http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbae4135c111d1829f0000e829fbfe/frameset.htm]).

  • Check Vendor Master when Creating Customer Master

    Hi,
    When we create customer master, we would like to check against vendor master for similar names so we can alert the user to link the customer to vendor (for contra purpose).
    Is there any standard checks we can configure?  If not, user either has to check manually or an enhancement has to be developed.
    Thanks.

    Hi, exit LXF05U01

  • Vendor capacity check when creating PO

    Hello Friends.
    We have a business process situation where we would like to check Vendor capacity at time of creating PO (NB) for raw materials to ensure that we do not place POs for more than Vendor capacity.
    Ideally it would be great if there is any way to check all open PO qty and compare with Vendor capacity at time of placing PO - converting PR to PO or direct PO creation.
    We are in ECC 6.00.
    Appreciates your comments/suggestions.
    Thanks,

    Thanks all for your comments but option for contract will not work in our case and here is the reason.
    We want to make sure that we do not have open PO qty more than what Vendor can supply at any point of time. Business reason is sometimes there is surge in finished goods demand and MRP will create new PRs for raw materials and planners will keep converting these PRs to PO withouth knowing how much open qty already Vendor has to supply. So if we have somewhere a check point in system where it checks and warn if open PO qty is more than particular limit set somewhere for example, PIR etc.
    Please comment.
    Thanks in advance - vbhai

  • Cenvat determination and vendor excise details are not checked in MIGO

    Hi experts,
    I have created one PO with Zero excise duty amounts (No excise duty) and following problem observed at the time of MIGO -
    System doesnt check any vendor excise details (excise indicator marked as ZERO in j1ID) even without entering excise invoice No and date in MIGO system accepts the entry with ZERO excise duty amounts.
    hence a fictitious part 1 No is generate by system for which no point taking part II.
    Kindly suggest
    Regards,
    Pawan

    Check  SAP  Note No 1282447-  check vendor excise details in MIGO .
    While capturing excise invoice along with the goods receipt process through
    the transaction MIGO, the system does not validate the existence of the
    excise details of the vendor master.
    This note introduces the error 8I 565, 'Excise Details are not maintanied
    for Vendor MIGO', when the vendor excise details are not maintained in
    J1ID.
    Raviraj.

  • Duplicate vendor Invoice check in FB60

    Hi Experts,
    I want to put the duplicate invoice check while posting the vendor invoice through FB60. I want the system to check the duplicate invoices in combination of the Vendor code and vendor invoice number ( we put the vendor invoice no. in the reference field of FB60 ). How to make this possible. I do not want to make the FI validation for the same. Can you please suggest how to go ahead with this.
    Thanks,
    BABA

    Hi Shailesh,
    phuu, ok, let's start from the beginning then.
    Some theory first:
    you need the validation because the standard check takes the doc.date ito consideration and this is not wanted. And you need the exit from the validation (! not a separate exit! not the original), locate the IF-statements where there is an ELSE option ending with function CUSTOMIZED_MESSAGE. It is up to you what to do here. In the original functoin module, the messages are issued here immediately. It can be an error or a warning, depending on the setting in table T100C. If my understanding is correct,  you always want to see an error message, bt this should be done in the validation, not in the function module. So you should skip the customized_message function call and just issue the messages here as info message regardless of T100C settings. In this case, remove the function call customized_message (as many times as it occurs) and issue the message included directly as an information. Right after the message was issued, set E_RC to 4, infoming the validation that the check has failed. (Note that the customized_message function is only called if the check has failed, so no worry that you always get the message.
    4. Define the exit for the validation
    =========================
    Go to your form pool Z_RGGBR000 (defined in V_T80D) and locate the statement APPEND EXITS. It should appear few times, locate the last occurence.
    Right after that, enter the following:
    exits-name = 'U901' .
    exits-param = c_exit_param_none.
    exits-title = text-901.
    append exits.
    This will define a new exit namd U901 for the validation routines. If in V_T80D, you already had a Z (or Y) report, check if the string U901 is used in that code already (check for the main program). If this is the case, instead of U901, use another name, it should begin with U followed by 3 digits. Also, you make sure the text symbol text-901 (or the 3 digits you are using) is existing, doubleclick it and enter a description like "Duplicate invoice check validation" or similar.
    Well, the exit is published, we have to write the main code now.
    go to the very end of your Z_RGGBR000 report and add a new form U901 like follows:
    Duplicate invoice check validation
    FORM U901 USING B_RESULT.
    Vendor master flag
    data: l_reprf like lfb1-reprf.
    Result of function module
    data: l_rc like sy-subrc.
    Check vendor master first
    select single reprf into l_reprf from lfb1 where bukrs = bkpf-bukrs and lifnr = bseg-lifnr.
    Do not continue if flag is not set.
    if L_REPRF is initial.
      b_result = b_true.
    endif.
    check not L_reprf is initial.
    Call modified function module
    CALL FUNCTION 'Z.....your function'
        EXPORTING
          i_bukrs = bkpf-bukrs
          i_lifnr = bseg-lifnr
          i_waers = bkpf-waers
          i_bldat = bkpf-bldat
          i_xblnr = bkpf-xblnr
          i_wrbtr = bseg-wrbtr
          i_koart = bseg-koart
          i_reprf = L_reprf
          i_shkzg = bseg-shkzg
          i_xumsw = bseg-xumsw
          i_bstat = bkpf-bstat
          i_belnr = bseg-belnr                                 
          i_gjahr = bkpf-gjahr                          
          i_blart = bkpf-blart
    EXPORTING
          e_rc = L_RC.                                
    Decide if validation message must be issued or not
    if L_RC = 4.
      b_result = b_false.
    else.
      b_result = b_true.
    endif.
    endform.
    After this, activate the source code. Make sure you have defined the text-symbol 901 before!
    5. Define the validation
    =================
    Go to OB28 now, and enter your company code(s) and the call-up point 002 (line item). If there is a validation defined already, you have to add a new step only, if not, you have to create the validation anew.
    I assume there is no validation defined yet, so enter a name for the validation like FI_2 or similar. It should NOT be named DUPLIC or similar, i.e., you should not include the purpose in the validation name. This is because the validation is defined on company code / call-up point level and it may contain many steps for different purposes later. A generic name FI-2 or probably your company code followed by 2 (2 is the call-up point) is the best choice.
    Before presing enter go to the last column Validatin active and enter 1 here.
    Then press enter and you will get an error that the validation does not exist. No problem, go to menu path Environment --> Validation and let's create a new validation.
    First, enter a description for your new validation in the right hand panel. Again, this should be a generic description, tell nothing about duplicate invoice checks here.
    You may be asked here to assign a message class to the boolean class 009. You should enter here a Z message class where the validation message should be issued from. If no appropriate message class exits, open a new session go to SE91, enter a new message class Z... press create, enter a description. Then go to the Messages tab there, and create a new message with number 001 (NOT 000) and enter the message text there. E.g. Duplicate entry not allowed.
    Coming back to the validation, if the message class was already assigned (this is the case if there was a validation defined earlier), you can create a new step. In case of a new validation, it will become the first step. But if there was already a validation in OB28 for your company code and call-up point 2, then it will be the last step. In the left hand panel, make sure the new (or existing) validation is selected and press the Create Step button (Ctrl-Shift-F5).
    In the right hand panel, enter a description for your step. This is the point where you can enter Double invoice check or similar.
    We have three parts here, a Prerequisite and a Check part, finally a message.
    In the left hand panel, select the Prerequiste. This will activate that screen block in the right side. We have to make sure that our validation is called only for the relevant vendor line items, so press Ctrl-F3 to hange to expert mode ) and enter the following in the Prerequiste window in the right hand panel:
    BSEG-LIFNR <> '' AND BSEG-XUMSW = 'X' AND BSEG-KOART = 'K' AND
    BKPF-BSTAT = ''
    Beware '' is a ' followed by another ' and not a single " !!
    Then switch back to normal mode using Ctrl-F1 and check the small lamp below that should be green now. Also, you can see the field descriptions now. If the lamp is red, press Ctrl-F3 again, delete all and copy the above again. Do not bother with line breaks. Switch to Ctrl-F1 again until the lamp is green. OK, what we have told here was please call the validation only if we have a vendor number and if this is a sales relevant item (invoice or credit memo, but not a payment or similar, this is the standard logic as well), and the account type is vendor (K) and this is a normal document.
    WHen you are done here and the lamp is green, then go to the left side again and select the Check part. Now you should be able to edit the Check screen lock in the right hand side again. Switch to expert mode and enter simply U901
    This is the name of the form in your Z_RGGBR000 report. NO brackets, no spaces, only U901 here. Switch back to Ctrl-F1 and instead of U901, you should see the text of your form (text symbol 901 in report Z_RGGBR000).
    Finally, click the Message part in the left side to be able to maintain the message in the right side. If you issued an error from the function module already, you can give here an information, or you can give it as an error if you like. The message number is one of the messages from your Z message class, you have to define the text in SE91 (see above).
    When done, save the validation and you can test it immediately.
    Here a brief summary what is happening:
    OB28 setting defines that in your company code a validation like FI-2 or similar is active on line item level. Whenever a line item is abut to be created, the validation will be called.
    However, the prerequisite of the validation is quite strict: only a limited number or vendor items will allow to continue, other line items (G/L, customer, not sales relevant vndor, etc.) will just skip the whole validation.
    If the prerequsite was met, the Check part is carried out. Here we have the exit U901.
    In the exit, first we check if the vendor is flagged for double invoie checks. If not, we quit and processing can be continued. B_TRUE means it is OK. If the vendor is flagged, we call the new Z function which is almost the same as the original one.
    The Z function will check table BSIP, but it will skip the document date comparison. If the current invoice seems to be entered earlier (regardless of the doc.date), instead of the standard customized message (which can be E or W for instance), the very same standard message will be issued as an information. So the user will be informed about the previous document number but the processing won't be stopped. In addition, a return code will be set to 4, meaning check has failed.
    Jumping back to the exit, if the return code is 4, we have to tell the validatin that the check has failed (B_RESULT = B_FALSE), otehrwise we can tell the validation that the check was OK (B_RESULT = B_TRUE).
    Now we are back in the validation, and, depending on B_RESULT, we just continue processing (B_TRUE), or issue an error message from a Z message class (B_FALSE). As the main standard message was isued already from the Z function, the user should know at this stage what the matter is. Your Z message can be a bit generic one, no need to include the vendor number or the previously issued invoice, etc.
    Hope that helps, points welcome
    Csaba

  • Vendor master file report.

    Dear All,
    I always use S_ALR_87012089 display changes to vendors to check vendor master data if they are created or updated in accordance with proper approvals (not a workflow in SAP).
    Recently, I see other tcode S_ALR_87012090, but do not know what is its use.
    Can you please let me know detail about S_ALR_87012090.
    Thanks
    Ndhoan

    Hello,
    The program S_ALR_87012090 displays changes to the sensitive fields (such as Bank Account, Bank control key etc. configured defined by us). The reviewer can confirm or refuse the changes interactively from the list produced by this report.
    Thanks,
    Venu

Maybe you are looking for