Vendor invoice number

where should i enter the vendor invoice number during invoice verification
i am not able to see any where the vendor invoice number which i entered in invoice verification
Pls guide me

Hi
Yo can enter your Invoice number in reference field in MIRO on basic tab
If you want report for invoice and vendor reference ( vendor invoice ) then you can get from following way
1) MIR5
2) from Po history tab in Po scroll at right hand side you will get reference for Invoice number
Regards
Kailas Ugale

Similar Messages

Vendor Invoice Number in FBl1n

Hi MM Gurus,
The client requires to have the Invoice Number which is generated at the time of LIV in FBL1n T. Code.
I am getting the Accounting Document Number of Invoice but not the Vendor Invoice Number. I have tried everything from the Change Layout Button but i am not able to get the Vendor Invoice Number in FBL1n T. Code.
Please suggest me for the same.
Thanks in advance.
Sure, Points will be assured.

hi,
Please search in FS00 control tab and field sort key.
if not there then use PO no there and by clicking on PO in po history tab u can see invoice no.
regards,
sujit

Vendor invoice number in FI

IN whihc table can i get the Vendor invoice number in FI
Thanks,
Mohammed.

EKBE where VGBEL = 2 for Vendor Invoice for PO
if u want to get Accouting document then u have to make use
<b>'AC_DOCUMENT_RECORD'</b>
Regards
Prabhu

Recurring Vendor Invoice- Number range problem

I am trying to setup recurring invoice entry through FBD1 for my company code abcd. I entered KR as document type. I have already set up number range which is 03 for KR. after entering all field data on the first screen when I click on "first entry data entry" or "account assignment model", I get an error message"saying "in company code abcd, the number range x1 is missing for the year".
I am not sure what I am doing wrong. My number range for KR is 03 and it is assigned to my company code abcd. Where is the 'X1" coming from? How i can resolve this?. Thank you for your advice.
Rashid

Hi Rashid,
In FBD1, you only create a recurring document and this document is only saved in the system, not posted. This recurring document will be used to post multiple documents later on when you run recurring documents through F.14
So logic is
FBD1 document - Only saved. Never posted. Recurring documents use X1 number range in standard system and you need to maintain X1 range in FBN1.
F.14 - When you run the above recurring document , document is posted and document type will be whatever you specify while creating recurring document in FBD1(KR in your case). System uses number range 03 when it posts a document from F.14
Assign points if useful
Thanks, Ashok

Report showing Invoice number, vendor,material and qty

Hi Guys
Is there any report where we can take report for vendor, invoice number, material and qty.
Regards

Dear
yeah! yau can check ME80FN with purchase order history setting.
full marks to me if solved
regdsd
dev...!

Shipment document number and cost document number for vendor invoice

Hi,
Given a Vendor invoice number ( MIRO) how to find out the shipment number and cost docuemnt number?
Regards,
Krishna prasad.

Hi,
Please try using SREL_GET_NEXT_RELATIONS. Please try to search on SDN and you should find an example fo this. The only thing you need to pass is the Business Object Name for Vendor Invoice number. Or if you have an alternal field like even PO that you can pass , that will be of great help as well.
You may want to take a look at:
SREL_DISPLAY_LIST_OF_NEIGHBORS
SREL_GET_NEXT_RELATIONS
Pls reward points if useful.
Thanks
Ganesh.S

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

How to find the invoice number from accounting document number?

Hi
I am using the bapi BAPI_AP_ACC_GETSTATEMENT and trying to get the invoice numbers of all the payments.
but i am unable to find the link between the accounting document number from the bapi and the vendor invoice number.
i have tried the tables BSE_CLR, BSEG and BKPF. the field AWKEY in BKPF has the combination of BELNR & BUKRS & GJAHR when the document type is anything other than RE.
How can i get the invoice numbers from the accounting doc. numbers?
Regards
Sujai

I am unable to find the link between BKPF-BELNR and RBKP-BELNR from the bapi return values.
XBLNR is blank when i check the table.
the output of the bapi is something like this
COMP VENDOR   CLEAR_DATE CLR_DOC_NO ALLOC_NMBR   FISC   DOC_NO     ITE
                                                                                1000    1100 ........ ......................................... 20020123           2002 1900000202   002
1000    1100 ........ .........................................20020123           2002 1900000203   002
1000    1100........ .........................................20020123           2002 1900000204   002
1000    1100........ .........................................20020123           2002 1900000205   002
now i try passing the doc_no (1900000XXX) and the fiscal year (2002) and company code to BKPF
the XBLNR field is blank. This document number sequence doesn't seem to be the accounting document number of the invoice coz that starts with 51XXXXXXXXX.
If i try passing the number with sequence 51XXX... to BKPF i get the invoice number there in the AWKEY field.
I am not sure what this sequence (19___) represents.
Sujai
Edited by: Sujai S on Nov 5, 2008 7:22 PM
Edited by: Sujai S on Nov 5, 2008 7:22 PM

FM : AC_DOCUMENT_RECORD for vendor invoices

Hi friends,
I am working on to get the accounting document from the vendor invoice which was created in tcode MIR4.
For this requirement, i am trying to use the FM AC_DOCUEMNT_RECORD.
I am passing the AWTYP = RMRP and the vendor invoice number. But it is resulting that no accounting documents available.
When i use the customer invoice created from VF03 and AWTYP = VBRK it is working fine.
Can any one let me know whether we can use this FM for vendor invoices or can we proceed with any other FM?
Thanks & Regards,
Prabu

Hi prabu,
Try giving the Vendor Invoice Number in AWREF as the variable AWTYP is a Reference Transaction((VBRK etc)
CALL FUNCTION 'AC_DOCUMENT_RECORD'
           EXPORTING
                i_awtyp      = t_ckmi-awtyp    " Reference Transaction
                i_awref      = t_ckmi-awref    " Reference Document Number   -
>
                i_aworg      = t_ckmi-aworg   "Reference Organizational Units
                i_awtyp_excl = t_ckmi-awtyp
         TABLES
               T_DOCUMENTS =
           EXCEPTIONS
                no_reference = 1
                no_document = 2.
      IF sy-subrc > 0.
        MESSAGE ID sy-msgid TYPE 'S' NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
Revert for further clarification
Thanks
Sri

Steps to upload vendor invoice(tcode fb60) in bdc

hi, iam srinivas can any one plz send me the steps to upload veneor invoice tcode is (fb60).i dont want the code but i want the steps to create .
thanks and regards.
Srinivas.

refer this site.
FI_AP_FBR2_Post_With_Reference (FBR2)
Business Process Description Overview
Use this procedure to copy a previously posted non-PO invoice document that uses many of the same values.
This may help reduce data entry time if used correctly. For example, the library invoice vouchers that have the same vendor but many invoices on them might be a good example of when to use this transaction code.
Trigger
Perform this procedure when there is an invoice that needs to have data entered where most of the fields are the same as a prior invoice document already entered in the system.
Prerequisites
·         Security Role: AP_DIR_INV_ENTRY
·         An FB60 invoice has already been data entered.
Menu Path
None
Transaction Code
FBR2
Tips and Tricks
·         If you would like to save this transaction under your "Favorites" folder, right-click on the "Favorites" folder, select "Insert Transaction" and type in this t-code when the box appears.
·         You may use the transaction code: search_sap_menu to search for a transaction codes menu path.
Procedure
Enter Vendor Invoice: Company Code PUR
Typically the FBR2 - Post With Reference transaction is accessed from the Financial transaction code that you just used. For Accounts Payable, typically we would use the FB60 transaction code to enter invoices that are not PO-related. After you have entered an invoice, you can now post a second invoice. Feel free to post an invoice in DEV to the Vendor ID number: 31. Choose today's date as the Invoice Date. Enter a Vendor Invoice in the Reference Field. Enter $1000 as the Amount. Enter a Text that you want to show on the remittance advice to the vendor. Choose your own GL Account and Cost Center. Enter 21010000 as the Fund. Make sure to also enter $1000 in the Amount in doc. curr. field.
    Please be aware that the FB60 screenshot above is using the ZPurdue Variant so unless you are also using that same variant the order of your columns may differ.
    Refer to FB60 documentation for more information regarding entering a non-PO related invoice.
    After an invoice has been entered, you may proceed to step 1. If you prefer not to enter an FB60 invoice then after you open FB60, immediately do step 1, but enter "1900001354" in the Document Number field.
1.       Select Goto Post with reference           Shift+F9 to go to the FBR2 transaction.
Post Document: Header Data
The document number you just entered in FB60 should now display. If you did not first enter your own FB60 invoice, please enter 1900001354 in the Document Number field. Make sure Company Code is PUR and Fiscal Year is 2007.
    If you did enter your own FB60 invoice to reference to, please be aware that the data entry fields will have different content in the screen shots than what you are seeing on your screen.
2.       Click or the "Enter" key to proceed.
Post Document: Header Data
Because we want to avoid paying the same invoice twice, we must change the reference field to another Vendor Invoice text.
3.       As required, complete/review the following fields:
Field Name
R/O/C
Description
Reference
R
Allows for further clarification of an entry by reference to other sources of information, either internal or external to SAP. Any SAP-posted document number can be used as a "reference" when entering a new document.
Example:          VENDORINVOICE#2
    Your reference number should be different than the one above. Otherwise, the system will think you are entering a duplicate invoice. Please change your text slightly.
Post Document: Header Data
4.       Click or the "Enter" key to proceed.
Post Document Display Overview
You are now viewing the document overview screen.
5.       Double-click to open that line item.
Post Document Correct Vendor item
When you open the Vendor line item, you may change the Text field here to change what appears on the remittance advice.
6.       As required, complete/review the following fields:
Field Name
R/O/C
Description
Text
O
Description field for an entry.
Example:          prints on remittance advice - for second invoice
Post Document Correct Vendor item
7.       Click to return to the document overview screen.
Post Document Display Overview
The document overview screen.
8.       Click to post this second invoice which has the same fields as the original except a different vendor invoice number and a different remittance advice text.
Information
Pending upon your user settings, you may not get this pop up box, but just a message in the bottom left hand corner of the screen.
9.       Click to close the box.
Enter Vendor Invoice: Company Code PUR
Because you used the menu (Goto Post with reference) from FB60 to access the FBR2 transaction code, you are then returned to the FB60 transaction after you have posted the invoice.
10.     Another way to access FBR2 is to just type the t-code in the field at the top of the screen. As required, complete/review the following fields:
Field Name
R/O/C
Description
Transaction Code
R
A unique four-character (in most cases) identification assigned to each SAP transaction based on its purpose.
Example:          /nfbr2
11.     Click or the "Enter" key to proceed.
Post Document: Header Data
The FBR2 transaction code opens with the last document number entered as the default.
12.     Click or the "Enter" key to proceed.
Post Document: Header Data
This time we will change the vendor number
13.     Change the Reference field. As required, complete/review the following fields:
Field Name
R/O/C
Description
Reference
R
Allows for further clarification of an entry by reference to other sources of information, either internal or external to SAP. Any SAP-posted document number can be used as a "reference" when entering a new document.
Example:          VENDORINVOICE
    Your reference number should be different than the one above. Otherwise, the system will think you are entering a duplicate invoice. Please change your text slightly.
Post Document: Header Data
14.     As required, complete/review the following fields:
Field Name
R/O/C
Description
Account
R
Unique identification number. SAP uses several kinds of accounts. SAP's general ledger accounts are similar to standard in most accounting systems. SAP also uses sub-ledger accounts for customers (accounts receivable), vendors (accounts payable), and assets (asset accounts). These sub-ledger accounts roll-up to a general ledger account.
Example:          5000129
    Vendor 5000129 in DEV has withholding tax applied to it in the vendor master.
Post Document: Header Data
15.     Click or the "Enter" key to proceed.
Post Document Add Vendor item
If the vendor invoice date was a date in the past, the due date for pay immediately will be in the past. You may get the above informational message to alert you of the date. If you do, just hit the "Enter" key to acknowledge it.
Enter Withholding Tax Information
Because this vendor has withholding tax information in its vendor master, you will receive this popup up box.
16.     Click to accept it.
    Refer to the Tax Department for more information regarding withholding tax.
Post Document Display Overview
You should now see the document overview screen. If you do not, then click on .
17.     Double-click OR click to open it.
Post Document Correct Vendor item
18.     As required, complete/review the following fields:
Field Name
R/O/C
Description
Text
O
Description field for an entry.
Example:          change remittance advice text
Post Document Correct Vendor item
19.     Click to view that Vendor's Withholding tax information again.
Enter Withholding Tax Information
    If for some reason, for this invoice the vendor should not have any withholdings, you would enter a 0.00 in both the W/Tax Base and W/Tax Amt fields.
    When using the FBR2 to change withholding tax amounts, you need to be very careful if using this new invoice as the "reference" invoice for the next one. For example, if you put 0.00 in both W/Tax Base and W/Tax Amt fields then if this is the reference invoice, those 0.00 amounts will automatically be applied to the next; however, you won't see the 0.00 displayed. The 0.00 will be assumed.
20.     Click to close the box.
Post Document Correct Vendor item
21.     Click to post the invoice.
Post Document: Header Data
Your new document number will display in the bottom left hand corner. Pending upon your user settings, you may also get a pop up box to acknowledge.
You have posted another invoice, but this time you changed the vendor ID used, the vendor invoice, and the text on the remittance advice.
    Notice that the "Document Number" field now defaults to the newly posted invoice number.
    Because you entered FBR2 in the transaction code field to access this screen, when you post an invoice you are returned to the beginning of the FBR2 screen. Remember, when you accessed it from the menu line of FB60? If you access it that way, you are then returned to FB60 after the Post with Reference document is posted.
22.     Because you are returned to the start of FBR2 again, you may just click or the "Enter" key to proceed.
Post Document: Header Data
Now you are at the start of entering a new invoice again.
23.     Click to return to the main menu without finishing the process of entering another invoice.
24.     You have completed this transaction.
Result
You have posted two documents by using a reference document. This reduced the data entry required since it defaults the fields from the reference document.
Comments
Be very careful using this transaction if you change withholding tax amounts.
To see the results/calculations of discounts and withholdings, you must run F110, the Payment Program.
http://www.purdue.edu/onepurduehelp/content/fi_ap_fbr2_post_with_reference/wi/html/index.htm
Message was edited by:
        Karthikeyan Pandurangan
Message was edited by:
        Karthikeyan Pandurangan

A/P Invoice Vendor Ref Number Field updating after adding the Invoice Copy

Hi All,
              I am able to change the Vendor Reference number in A/P Invoice Document after adding the Document. I want to restrict this to happen. Plzz help how to do this????
Regards,
Sree.

1.The Modify Posted A/P Documents authorization refers to some fields only, e.g. the Due Date or Pay to address.
2. Additional authorization can be defined only for full forms, not for fields.
3. The SP Joseph suggests will refuse those modifications when the Vendor ref is empty.
To avoid modifying the Vendor ref you can use this code:
IF @Object_type = N'18' and @transaction_type = N'U'
BEGIN
declare @li int
set @li=
(select max(t.LogInstanc)
   from ADOC t
   where t.ObjType=18 and t.DocEntry=@list_of_cols_val_tab_del)
IF
   (select isnull(t.NumAtCard,'')
    from ADOC t
    where t.ObjType=18 and t.DocEntry=@list_of_cols_val_tab_del
      and t.LogInstanc=@li-1)
!=(select isnull(t.NumAtCard,'')
   from OPCH t
   where t.DocEntry=@list_of_cols_val_tab_del)
begin
Set @error = 10
Set @error_message = N'Vendor refernce not modifiable !'
end
END
Or if you want to allow modifying an unfilled reference, then this:
IF @Object_type = N'18' and @transaction_type = N'U'
BEGIN
declare @li int
declare @pref nvarchar(100)
set @li=
(select max(t.LogInstanc)
   from ADOC t
   where t.ObjType=18 and t.DocEntry=@list_of_cols_val_tab_del)
set @pref=
(select isnull(t.NumAtCard,'')
    from ADOC t
    where t.ObjType=18 and t.DocEntry=@list_of_cols_val_tab_del
      and t.LogInstanc=@li-1)
If @pref !='' and @pref !=
(select isnull(t.NumAtCard,'')
   from OPCH t
   where t.DocEntry=@list_of_cols_val_tab_del)
begin
Set @error = 10
Set @error_message = N'Filled vendor refernce not modifiable !'
end
END

Vendor Invoice with Same Reference Number in two fiscal years.

Vendor Invoice entered in SAP.
DocumentNum 1600000612 Reference "47026723WA" Vendor Number "637278" Year "2008"
DocumentNum 1600000667 Reference "47026723WA" Vendor Number "637278" Year "2009"
We are thinking SAP will not allow/generate invoice with same Reference number. How can we restrict from entering Vendor invoices with Same Reference Number from same Vendor.
Thanks
Raghuram

Restrict it through message control
Transaction code OBA5
Message NO.121
Make it error for batch and online.
Thanks,
Ravi

Open the field purchase document number in vendor invoice

Hi,
I've to open the purchase document number field in the vendor invoice transaction (FB60) for the reconciliation vendor account?
I've done these operations in customizing:
- set the field purchase order in the Field status group like optional
- set the tield purchase order in the posting key control (31 and 21)
Could you suggest me how to open the field?
Tks!
Regards,
Gaetano

Hi,
Can you please provide me the solution for this as I too am facing a similar problem. While posting an entry using FB01/F-43, for posting key 31(Vendor Invoice), despite making Purchasing Document field optional in field status group of the posting key as well as Reconciliation (GL) Account, the Purchasing Document field is not appearing.
Thanks and Regards,
Sumita

Vendor Part number on Invoice

hi All,
Is there any possibility to check the vendor part number while posting the invoice? I per my knowledge we maintain this vendor partnumber in info record. And while creating the PO we can check it in material data.
My question is is there any setting to check the vendor part number while doing miro? Is this setting is dcoument specific? & where in SPRO we have to do it?
Amit

Hi Amit,
In your case if you use MPN material PO will reflect the Vendor Part No.
Ang in stock there will master material (which is your part no)
So no need to check againin MIRO for part no.
Hope this will solve your problem
Thanka and regards
Gitesh

A/P Invoice Document Vendor Reference Number field..................

Hi All,
            I have a senario:
        I have Posted A/P Invoice With Vendor XXX, Vendor Reference number is 111. I should be able to post another A/P Invoice using the same Vendor Reference number-111 but Vendor is YYY.
    But I should not be able to post same vendor reference number - 111 in two A/P invoices where the vendor is same. (Say Vendor is XXX).
        How do I satisfy these two conditions??????
Regards,
Sree.

Hi Sree,
SAP Business one will not allow you to to have the same reference number even if it is for another supplier.
This is known SAP validation.
Regards,
Rakesh

Vendor invoice number

Similar Messages

Maybe you are looking for