Vendor invoice print

Hi sap gurus,
I want stndard T code for Vendor invoice print.plz give me if it is possible in SAP

Transaction code to print invoice :MR90
For this you need to configure output determination in SPRO>Materials Management>Logistics Invoice Verification-->Message Determination.

Similar Messages

F110 prints the check on the wrong page/leaf when vendor invoices overflow

Hi all,
When paying vendor invoices with a check printed through F110, if a vendor has more invoices than fit on a single check leaf, the following should happen:
- Invoices overflow to the next page
- Any checks before the last one are left blank and voided by the system
- The check on the last page is printed with the total amount and is marked as valid by the system
However, what's happening is the following:
- Invoices overflow to the second page
- The check on the first page is printed with the amount, date, etc. and marked as void by the system
- The check on the second page comes out blank and is marked as valid by the system
For some reason the form or print program isn't waiting until the last page to print the check. I can't find anything about check printing in case of an overflow in SAP Notes or transaction FBZP. Is this controlled by a setting in the program variant, or somewhere else?
Thanks!
Edited by: Pedro G. on Sep 9, 2010 5:43 PM

Thanks for the reply, Brad.
I see the CHECK window on the FIRST page has text elements 540 and 545, but the rest of the lines are commented out. There seems to be nothing printing there. Instead, this particular check layout has the date and payee in one window and the amount in another one, both on the FIRST page of the SAPscript, but there are no calls to WRITE_FORM for either of those two windows. Does the CHECK window have any special properties that (should) cause it to always print at the end, and could I then apply those properties to these other two windows to fix the problem?
As for the debugger, I guess what I should be looking for is the moment when the check gets printed, and see what happened exactly before that triggered it? Then see if I can delay that trigger until the end?

Print-off the scanned images for vendor invoices

Required report.
Print-off the scanned images for vendor invoices
Basically, his selection screen will be:
Vendor Invoice XXXXXXXXXX to XXXXXXXXXX
Once the user executes the program a list of invoices is presented to the screen.
Then the user will be able to select one or several of these invoices and click a print button.
However, the attachments are stored in Adobe .pdf format.
Kind Regards
Mark H,

Hi,
Write a report to fetch the data from Tables RBKP and RSEG for the vendor INvoices, based on the Invoice No(BELNR) entered on the Selection screen.
display them with the required fields on the first list. Take a single CHAR field in the internal table for CHECK BOX and display that Internal Table fields.
Keep buttons (SELECT and PRINT) on the MENU of the output screen for processing the selected records on the output and printing the selected records in the interactive report using AT USER-COMMAND function.
reward if useful
regards,
ANJI

Print of vendor invoice

hi gurus,
I an not able to take printout of my documents (vendor invoice) t-code f-43 . thr is no problem while creating the vendor invoice but when i try to take the print it shows the error "Spool request (Number xxxxxxx) created without immediate output." plz suggest wat to do.
its urgent.

Dear Jaswant,
for this you goto to SP01 there enter you r pool request no what u got then exicute ofter that click on check box then direct print.
it will help full to u.

Tables for vendor invoice and payment

Hi Gurus.
I want to know from which tables i can get the information for folllowing points.
1. Vendor Invoices - Complete (Header and Item)
2. Vendor Payments Details Detail about payment method (check, wire, etc)
Please tell me tje table names.

There is no specific table for header/item data for vendor invoice. Various information regarding vendor invoice (FB60) are stored in the following tables( note: Ignore the structures in the list ).
|Table Name |Table Description |
|/BEV3/CHKOMPAZVV |Append Structure CH -> CO PA |
|/CWM/ACCIT |Append Structure for Enhancement of Structure ACCIT in CWM |
|/CWM/KOMP |Catch Weight Management Enhancement |
|/DSD/TAXJURCD |Ship From Tax Jurisdiction Code: for Header Prc Comm Str |
|/SAPNEA/J_SC_LFA1 |Subcontractor Information |
|/SAPNEA/J_SC_LFB1 |Subcontracting Management |
|/SAPPSPRO/A_FI2_LONGNUM |IBU-PS: Append structure for structure NONBSEG |
|/SAPPSPRO/A_LONGNUMBER |additional fields for SPIIN number |
|/SAPPSPRO/EADD |Purchasing Document Header: Additional Data |
|/SAPPSPRO/EADD_DATA |Purchasing Document Header: Data Part Additional Information|
|/VSO/R_KNA1_A |Append to KNA1 for Vehicle Space Optimization |
|/VSO/R_KNA1_I |Additional Data for Vehicle Space Optimization for KNA1 |
|AACCHD_FMFG |US federal fields |
|AACCHD_PSO |IS-PS: ACCHD Append Structure for Payment Requests |
|AACCIT_GM |Append for Grants Management |
|AACCIT_PSO |IS-PS: ACCIT Append Structure for Payment Requests |
|AACCIT_SSP |Append for Payment Statistical Sampling Process |
|AACCIT_USFG |Append structure for US federal government |
|AAUSZ_CLR_USFG |Clearing information for US Fed (Tresury Confirmation) |
|ABKPF_PSO |IS-PS: BKPF Append Structure for Payment Requests |
|ABKPF_UMB |IS-PS: Append Structure for Transfer Transaction FMITPO |
|ABSID_PSO |IS-PS: Data appendix of open items customers |
|ABSIK_PSO |IS-PS: Data appendix of open items vendors |
|ABSIS_PSO |Local Authorities |
|ABUZ |Help Structure for Line Items to be Generated Automatically |
|ACCCR |Accounting Interface: Currency Information |
|ACCCR_FKEY |Key: Acctg Currency Data for Line Item Including Currency |
|ACCCR_KEY |Key: Accounting Currency Data for Line Item |
|ACCFI |Interface to Accounting: Financial Acctg One-Time Accts |
|ACCHD |Interface to Accounting: Header Information |
|ACCHD_KEY |Key: FI/CO Document Header |
|ACCIT |Accounting Interface: Item Information |
|ACCIT_EXTENSION |ACC Document: Additional Item Information |
|ACCIT_JV |Joint Venture Accounting |
|ACCIT_KEY |Key: FI/CO Line Item |
|ACCIT_WT |Withholding tax information for FI Interface |
|ACCRDF |Fields for Posting Small Differences: Preparation |
|ACC_DOCUMENT |Accounting document |
|ACC_KONTEXT |Context Info for FI Single Screen Transactions FB50 and FB60|
|ACERRLOG |Return Parameter |
|ACGL_HEAD |Fields for Document Header Entry Screen |
|ACGL_ITEM |Structure for Table Control: G/L Account Entry |
|ACSCR |Communication Structure for Field Modification SAPLFDCB |
|ACSPLT |Carrier for Split Information re: Current Account Line Items|
|ACSPLT_WTNEW |Proportion of New Withholding Tax |
|ACSPLT_WTOLD |Proportion of Old Withholding Tax |
|ADDR1_SEL |Address selection parameter |
|AEBPP_KNBK |Additional Fields Bank Data Biller Direct |
|AEBPP_LFBK |Additional Fields Bank Data Biller Direct |
|AFMIOI |Append for new fields ECC50/ERP |
|AFMIOI_USFG | SD order needs quantity |
|AFMISPS |Additional Fields for Table FMISPS |
|AFM_ACCIT_EXTENSION |Extension for FM Payment Update |
|AFM_FAGL_GLT0_ACCIT_EXT |Extension FM Account Assignments |
|AFM_FI_BKPF_SUBST |Append to Structure BKPF_SUBST |
|AFM_FMFCTF |Append for Fund Center substrings |
|AFM_FMFINCODE |Append for Fund substrings |
|AIFM01D |Append for IFM01D |
|AKNA1_FMFG |US Federal Government Customer Master Data Additional Fields|
|AKNA1_PSO |Local Authority Additional Fields |
|AKNB1_PSO |IS-PS: Customer Master Record, Additional Data (Co.Code) |
|AKNBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALFA1_FMFG |US Federal Government Vendor Master Data Additional Fields |
|ALFA1_PSO |Local Authority Additional Fields (Address) |
|ALFB1_FMFG |PS fields for company code-specific master data field |
|ALFB1_PSO |IS-PS: Data Appendix Vendor Master Record (Company Code) |
|ALFBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALVDYNP |ALV dialog screen fields |
|ALV_S_FCAT |Field Catalog (for LVC and for KKBLO) |
|ALV_S_FILT |Filter Criteria (for LVC and for KKBLO) |
|ALV_S_GRPL |Group Levels (for LVC and for KKBLO) |
|ALV_S_LAYO |Layout (for LVC and for KKBLO) |
|ALV_S_PCTL |Structure for Checking Print in ALV |
|ALV_S_PRNT |Print settings (for LVC and KKBLO) |
|ALV_S_QINF |Structure for Quickinfos of Exceptions |
|ALV_S_SGRP |Field Groups (for LVC and for KKBLO) |
|ALV_S_SORT |Sort Criteria (for LVC and for KKBLO) |
|ANBZ |Help structure for asset line item |
|ANLZACCOUNT |Additional Account Assignment Objects in Asset Accounting |
|ANLZACCOUNT_FKBER |Account Assignment Objects: ANLZACCOUNT with Function Added |
|ARC_PARAMS |ImageLink structure |
|AT003_XBLNR2 |Append structure for US federal government |
|AUSZ1 |Clearing Table 1 |
|AUSZ2 |Clearing Table 2 |
|AUSZ_CLR |Assign Clearing Item to Cleared Items |
|AUSZ_CLR_ASGMT |Assgt of Clrg Items - Cleared Items with Acct Assignment |
|AUSZ_INFO |Open item data for clearing transactions |
|AVBKPF_FMFG |US federal |
|AVBKPF_PSO |IS-PS: Append Structure VBKPF for Payment Requests |
|AVBSEGDPSO |IS-PS: Append Structure VBSEGD for Payment Requests |
|AVBSEGKPSO |IS-PS: Append Structure VBSEGK for Payment Requests |
|AVIK |Payment Advice Header |
|AVIP |Payment Advice Line Item |
|BALHDR |Application log: log header |
|BALMT |Application Log: Structure for a formatted message |
|BAL_S_CLBK |Application Log: Return routine definition |
|BAL_S_CONT |Application Log: Context |
|BAL_S_MSG |Application Log: Message Data |
|BAL_S_PAR |Application Log: Parameter Name and Value |
|BAL_S_PARM |Application log: Parameters |
|BAPIASCONT |Business Document Service: File Content ASCII |
|BAPIBDS01 |Business Document Service: Reference Structure for BAPIs |
|BAPICOMFIL |BDS: Command File for Transport Entries |
|BAPICOMPO2 |SBDS: Enhanced Component Information |
|BAPICOMPO3 |SBDS: Enhanced Component Information |
|BAPICOMPON |Business Document Service: Component Table |
|BAPICONNEC |BDS: Structure for BDS Links |
|BAPICONTEN |Business Document Service: File Content |
|BAPIDPROPT |BDS: Structure for Properties |
|BAPIFILES |Business Document Services: Transfer Table for File Names |
|BAPIPROPER |BDS: Structure for Properties |
|BAPIPROPTL |BDS: Structure for KPRO Properties |
|BAPIQUERY |BDS Structure for Query Table |
|BAPIRELAT |Business Document Service: Relations |
|BAPIRET1 |Return Parameter |
|BAPIRETURN |Return Parameter |
|BAPISIGNAT |Business Document Service: Signature Table |
|BAPISRELAT |Business Document Service: Relationship Table with Signature|
|BAPIURI |Business Document Service: URI Table |
|BDCMSGCOLL |Collecting messages in the SAP System |
|BDCRUN |Batch input: Runtime analysis |
|BDIDOCSTAT |ALE IDoc status (subset of all IDoc status fields) |
|BDI_SER |Serialization objects for one/several IDocs |
|BDN_FKT |Business Document Navigator: Functions to be Excluded |
|BDWFAP_PAR |Parameters for application function module - IDoc inbound |
|BDWFRETVAR |Assignment of IDoc or document no. to method parameter |
|BDWF_PARAM |Parameters for workflow methods for IDoc inbound processing |
|BKDF |Document Header Supplement for Recurring Entry |
|BKDF_SUBST |Process Interfaces: Substitutable fields during posting |
|BKORM |Accounting Correspondence Requests |
|BKP1 |Document Header Supplement for Update |
|BKPF |Accounting Document Header |
|BKPFBU_ALV |Document Overview: Display Document Headers in ALV Grid Ctrl|
|BKPF_CARD |Credit Card: Append for BKPF |
|BKPF_LINE |Item Category for XBKPF_TAB |
|BKPF_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BKPF_USFED |Append structure for US federal government |
|BLNTAB |Document Number Table for Financial Accounting |
|BNKA |Bank master record |
|BNKAAPP |Appendix to Table BNKA |
|BNKT |Conversion of temporary to internal bank keys |
|BOOLE |Boolean variable |
|BSEC |One-Time Account Data Document Segment |
|BSEC_LINE |Item Category for XBSEC_TAB |
|BSED |Bill of Exchange Fields Document Segment |
|BSEE |Changeable Fields in the Line Item |
|BSEG |Accounting Document Segment |
|BSEGL |Document Segment: Fields Derived for Line Layout Variant |
|BSEGS |G/L Item Transfer Structure for Single Screen Transactions |
|BSEGT |Transfer Table for the Tax Postings to be Generated |
|BSEGZ |Financial Acctg Doc.Segment: Extras and Temp. Storage Fields|
|BSEG_ALV |Document Overview: Document Item Display in ALV Grid Control|
|BSEG_LINE |Item Category for XBSEG_TAB |
|BSEG_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BSET |Tax Data Document Segment |
|BSEU |Line Item Additional Information (Update) |
|BSEZ |Line Item Additional Information (Online) |
|BSEZ_LINE |Line Item Category for XBSEZ_TAB |
|BSID |Accounting: Secondary Index for Customers |
|BSIK |Accounting: Secondary Index for Vendors |
|BSIP |Index for Vendor Validation of Double Documents |
|BSIS |Accounting: Secondary Index for G/L Accounts |
|BSIX |Index table for customer bills of exchange used |
|BTXKDF |Fields for Exch.Rate Difference Posting for Taxes |
|BVOR |Intercompany posting procedures |
|CACS_A_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_A_CUST_COND |Commissions: Customer Fields Condition Technique |
|CACS_A_FIELDSPRICING |Append for Condition Technique Fields from Commission System|
|CACS_S_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_S_CUST_COND |Condition Attributes |
|CACS_S_FIELDSPRICING |Comm.: All Condition Technique-Relevant Commission Fields |
|CACS_S_FSINS |Customer Fields for Condition Technique of Insurances |
|CCDATA |Payment cards: Database fields relevant to both SD and FI |
|CFW_LINK |CFW: Link Info of a Container |
|CI_COBL |Extension |
|CKI_ACCIT_ML |Transfer from MM to ML in accit-structure |
|CNTLSTRLIS |Control stream list |
|COBK |CO Object: Document Header |
|COBK_ONLY |Non-key fields only in COBK (INCLUDE structure) |
|COBL |Coding Block |
|COBLF |Coding block: Tax table structure |
|COBL_COKZ |Assignment types for CO account assignments |
|COBL_DB_INCLUDE |Include with Additional Account Assignments for DB Tables |
|COBL_EX |Coding Block for External Applications (Not CO/FI) |
|COBL_FI |Fields from COBL that Must not Be Overwritten in FI |
|COBL_FM |Additional Fields for FM |
|D010SINF |Generated Table for View D010SINF |
|D020S |System table D020S (screen sources) |
|D020T |Screen Short Description |
|DBSEG |Dialog Supplementation BSEG (Taxes) |
|DD02L |SAP Tables |
|DD03P |Structure |
|DD03V |Table fields view |
|DD07V |Generated Table for View DD07V |
|DD23L |Matchcode ID |
|DD32P |Interface structure for search help parameters |
|DDSHDEFLT |Description of a default value for search help fields |
|DDSHDESCR |Interface: elementary search helps of a search help |
|DDSHFPROP |Characteristics of search help parameters |
|DDSHIFACE |Interface description of a F4 help method |
|DDSHRETVAL |Interface Structure Search Help <-> Help System |
|DDSHSELOPT |Selection options for value selection with search help |
|DDSUX030L |Nametab Header, Database Structure DDNTT |
|DDSUX031L |Nametab Structure, Database Structure DDNTF |
|DDTYPES |Table of all Dictionary types and classes |
|DFIES |DD Interface: Table Fields for DDIF_FIELDINFO_GET |
|DISVARIANT |Layout (External Use) |
|DOKHL |Documentation: Headers |
|DPPROPS |General property structure for data provider |
|DTC_S_LAYO |Structure for Design of Double Table Control |
|DTC_S_TC |Structure for table controls in the double table dialog box |
|DTC_S_TS |Tab Title Structure |
|DYNPREAD |Fields of the current screen (with values) |
|E071 |Change & Transport System: Object Entries of Requests/Tasks |
|E071K |Change & Transport System: Key Entries of Requests/Tasks |
|EAPS_20 |Field Enhancements for EA-PS 2.0 |
|EDIDC |Control record (IDoc) |
|EDIDS |Status Record (IDoc) |
|EDIFCT |IDoc: Assignment of FM to log. message and IDoc type |
|EDIMESSAGE |Transfer Structure with all Sy Fields for T100 |
|EDI_DS |Status record for interface to EDI subsystem |
|EDI_HELP |Help Structure for Reference Fields in EDI Function Groups |
|EK05A |Communication Area Purchasing - Financial Accounting |
|ESKN |Account Assignment in Service Package |
|EUDB |Development Environment Objects |
|EUOBJ |Workbench: Development Objects |
|EXCLTAB_LINE |Lines of EXCLTAB with OK Code to be Deactivated |
|EXISTING_DOC |Original Document |
|F05ACTRL |Control Fields for SAPMF05A and Subprograms |
|FAGLBSEGL_S |Additional Sender Flds from General Ledger for Doc. Overview|
|FAGL_GLT0_ACCIT_EXT |Line Information for Document Splitting |
|FAGL_MIG_S_BUKRS_LEDGER |Combination of Company Code and Assigned Ledgers |
|FAGL_SPLIT_FLD_S |Characteristics Permitted for Split |
|FAGL_S_APPLICATION |Application and Subapplication |
|FAGL_S_BALDIM |G/L Characteristics of Document Split in New General Ledger |
|FAGL_S_BUKRS |Structure with Company Code |
|FAGL_S_BUKRS_EXT |Structure: Company Codes --> Ledgers |
|FAGL_S_CURTYPES |Currency Types of a Ledger |
|FAGL_S_MIG_001 |Structure for Table FAGL_MIG_001 & FAGL_MIG_001_S |
|FAGL_S_MIG_MGPLN_EXT |Structure: Extended Migration Plan Information |
|FAGL_S_T8G40_BS |Split Fields with Characteristic "Balance Sheet" |
|FCRD_VBKPF |Credit Card: Include for Appends for BKPF, VBKPF |
|FCRD_VBSEG |Include for Appends for VBSE* |
|FDM_AR_CASE_ATTR_1 |FSCM DM: |
|FDM_AR_LINE_ITEM |FSCM: DM |
|FDM_AR_RFPOS |FSCM-DM: Enhancemt of Line Item Disp. with Dispute Case Flds|
|FELD |Screen Painter fields (internal) |
|FICCO |Adjustment Values for External Document Items |
|FICCT |Totals Information for Interclient Posting |
|FICTX |Tax Information for ICT |
|FIELDINFO |Field attributes for a specific field |
|FIN1_PARAM |OBNG: Trans. structure for official doc. numbering (global) |
|FIN1_PARAM_FI |OBNG: FI parameters |
|FIN1_PARAM_MM |OBNG: MM Parameters |
|FIPEX_STRUC |Subfields Commitment Item |
|FIPOEXT |Help structure for line items to be generated automatically |
|FIREVDOC |Transfer Structure for Dialog Module FI_DOCUMENT_REVERS |
|FISTL_STRUC |Substructure Fund Center |
|FM01 |Financial Management Areas |
|FMBLSTRING_COMPONENTS |Component of the BL String |
|FMCI |Commitment items master data |
|FMDY |FIFM: Screen Fields |
|FMFCTR |Funds Center Master Record |
|FMFG_ACCIT_EXTENSION |Extention for all fields that have to be transfered into BL |
|FMFINCODE |FIFM: Financing code |
|FMFPO |FIFM: Commitment Item |
|FMHRBA_NEG_DOC_TYPES |HR Integration: Doc. Types for Negative Funds Commitments |
|FMHRBA_SETTINGS |Integration with HR: Settings |
|FMHRBA_VAD_SETTINGS |HR Integration: Generate Value Adjustment Docs for Changes |
|FMICCN |FM: Append Structure for FMIOI (CCN Fields) |
|FMIDATA |Common Data for Funds Management Actual Data |
|FMIDATAFI |Clean FI Data for Funds Management Actual Data |
|FMIDATAOI |Clean Open Item Data for Funds Management Actual Data |
|FMIFIIT |FI Line Item Table in Funds Management |
|FMIKEY |Common Key for Funds Management Actual Data |
|FMIKEYFI |FI - Key for Funds Management Actual Data |
|FMIKEYOI |Common Key for Funds Management Actual Data |
|FMIOI |Commitment Documents Funds Management |
|FMIOIKEY |Key for Table FMIOI |
|FMIOI_USFG | SD order needs quantity |
|FMIREF |Ref. Funds Management Actual Data to Preceding Document |
|FMISPS |General Parameters for Funds Management |
|FMIT |Totals Table for Funds Management |
|FMMRESERV |Include for the Reduction of Funds Reservations (FM) |
|FMRFC |Function Modules and their RFC Destinations |
|FMSP_SPLIT_FIELDS |PSM Fields used in multiple account splitting |
|FMT001 |Additional Customizing for Funds Management |
|FMUP00T |Update Profiles |
|FMUP01 |Update Control with Value Type Dependency |
|FMUP_INV_KEY |Extension for FM Update: FI Key of Invoice |
|FMUP_PAY_KEY |Extension for FM Update: FI Key of Payment |
|FS006 |Fields for Optical Archiving |
|FTCHECK |Foreign Trade: Import Simulation - Ctrl Fields for Pricing |
|FTEXTS |Communication Structure for Additional Components |
|FTGENERAL |Foreign Trade: General Fields Item |
|FUND_STRUC |Substructure Fonds |
|FVD_TZB0A |Append to TZBOA: Loans Fields |
|GLACCOUNT_CCODE |G/L Account Master Record: Company Code |
|GLACCOUNT_CCODE_DATA |G/L Account Master Record: Company Code - Data |
|GLACCOUNT_CCODE_INFO |G/L Account Master Record: Company Code - Information |
|GLACCOUNT_CCODE_KEY |G/L Account Master Record: Company Code - Key |
|GLX_ORG_INFO |Organizational Assignment |
|GMBSEGZ |Grants Management Add-on |
|GXXLT_H |XXL interface: horizontal features |
|GXXLT_O |XXL_interface: texts for online display |
|GXXLT_S |XXL interface: structure of the semantics table |
|GXXLT_V |XXL interface: vertical features |
|HELPVAL |Restrict Value Range - Transfer Table |
|HELP_INFO |Transfer Values for the Help Processor |
|HELP_VALUE |Structure or Function Module HELP_VALUE_GET_FOR_TABLE |
|HHM_COBL |Include for COBL from FM |
|IADDR_PSO |Local Authority Additional Fields (Address) |
|IBKPF_PSO |IS-PS: Include Structure BKPF Payment Request Doc.Header |
|ICDIND |Structures for generating change document update programs |
|ICON |Icons table |
|ICONS |Icons |
|ICURR |Interface for Currency Translation

Incoming Excise Invoice - Print Layout Design

Dear all,
        How to prepare the Incoming Excise Invoice Print Layout Design.
        That Excise is Dealers Invoice.
        For Ex: 'X' is the one material , this has defined in material master as Inventory , Purchase and Sales item and its Excisable material.
       Ths 'X' material purchase from the vendor and selling to the customer.
       At the time sales for incoming excise invoice, in that invoice should include the what is purchases of that material and what is sales?
     This information how to bring the Print Layout Design at Incoming Excise Invoice.
         Please guide to me
Warm Regards,
K.Prasad,
+919921525560.

At first you have to check the Excisable in Item master for doing excise transactions.
Incoming Excise Invoice can be generated after doing Goods Receipt Transactions.
From Copy to Option Goto >> Incoming Excise Invoice >> the invoice form will be opened
From here you can select the PLD icon and design the layout you need.
come back here if any queries

Vendor Invoice Not displayed:

Dear Friends:
Using T.code: S_ALR_87012083 - List of Vendor Open Items for Printing, I am unable to find the Vendor Invoice No:
The customer wants to see the invoice no and details also.Is this possible.Please suggest of workaround also is welcome.
thanks&regards
msreddy

Hi Sridhar,
Please check this t/code.
FBL1/FBL1N
FK10/FK10N/FK10NA
F.98
FQUK
Hope this will help.
Regarsd,
Ferry Lianto
Please reward points if helpful.

Creating Check Manually for Vendor Invoice

I want to create a Check in SAP from a Vendor invoice manually. What steps do I need to take to do so?
I am creating vendor invoice in FB60
I can create a outgoing Payment F-07
How do I create a Payment document in reference to the vendor invoice?
I can create a check using FCH5 once I have the payment document.
Please suggest.

Hi
You following the correct steps.
When you will make a payment for an invoice, the invoice will be cleared throught the payment doc. Thats how the payment doc is referenced to invoice.
Since you are doing manual payment, you can manually enter the invoice number in the reference field of the payment document for future reference.
Coming to Check creation when you create a check for a payment document through FCH5. The check number get link to the payment doc in SAP. you can view this in tcode FCH2, here give the payment doc.
For future reference, you can populate any free field (reference, assignment, ref key3) in your payment doc with the check number assigned to it through tcode FCHU.
To print the check you can use the std program RFFOUS_C. Make sure the form that you use to print the check meets your requirement if using the std forms.
Regards
Nikhil

How to clear the down payment against the vendor invoice in the payment program?

A down payment is made $25 Later an invoice is posted for $100 Now i want to Pay $75 to Vendor But the Automatic payment program is not clearing the down payment against the vendor invoice. Could you please help how to clear the down payment against the vendor invoice in the payment program?

Swathi,
Need your help i have a strange situation
1) F-48 and document posted with document no = 15..... in company code = L002 with payment block getting populated automatically
2) F-48 and document posted with document no= 15..... in company code = Us11 without payment block and the screen does not even show payment block, I had to check this from BSEG table
My question is
a) How and where does this payment block is triggered through configured and how to process next steps.
b) when I use F-48, how do we do the actual payment, is there a check printing and linking it to the KZ document or is check printing done outside the system and the KZ document type does not have any linkage.
c) If I do FB60 for a higher amount how do we pay partial amount.
Your response is appreciated.

F-58 Error. vendor name printed but not Alternative payee

Dear group members
_Vendor name printed but not the name i entered in Individual set_
I followed Thread vendor name changed at the time of taking cheque printing
I made the below Transaction
1. I made the changes in vendor master under the head Payment transaction tab, in Alternative payer in document i selected check box of Individual entries
2. Posted in FB60 vendor invoice under payment tab check box Individual payee is selected, i entered alternative name so that check is printed in this name
3.In payment F-58 post & print i selected open item for payment after simulation i saved .The check is printed as per the
Name in Vendor master data but not the name i entered in Individ.setin fb60
I am not able to make to make payment, guide me
Your advice on this will be highly appreciated
Regards
shamulheq

Hi MUKTAKUMARI
I entered the bank details in the individual payee while entering FB60, the name coming in indiviid .set
In F-58 I made simulation Pk 50 QNB -Checks Payable & PK 25 vendor name, when i double click on the 2nd line item i found the name what mentioned in the Individ.set
I saved the transaction but the check was printed in the name of vendor master but not in the name i entered in indiviid set
Help me out to get the check printed in the individ set
Regards
shamulheq

Central bank indicator in Norwegian vendor invoice

Hi all
We plan to use the Telepay file format for our norwegian subsidiary.
The flat file seems is compliant with the bank requirements except
that at the begininng, for the Regulatory reporting codes and
descriptions (line BETFOR04 167-172 and 173-232), we had to define them in the State Central Bank Indicator customizing.
Unless I am wrong, there is no way to have automatically
this State Central Bank Indicator defaulted when entering the vendor invoice as it is for the withholding tax code for instance.
So it seems that whenever we enter a foreign vendor invoice, we always have to fill manually this field Central Bank Indicator (BSEG-LZBKZ).
Is that the normal SAP process in Norway or can it be done another way ?
Thanks

I did this customizing for a German client. Never knew it is used in Norway as well.
You are right, it has to be entered manually in line items. Here is what SAP says about SCB Indicator (I highlighted the relevant text).
Define SCB Indicator for Foreign Trade Regulations
In this activity, you define information using an indicator which is needed for reporting according to German foreign trade regulations (AWV) for foreign payment transactions and which shows the reason for payment. You must enter the indicator in the line item. The reasons for payment stored for the indicator are transferred when you print the form or in the corresponding data medium exchange.
Activities
Enter the required reasons for payment using an indicator.

Customer Invoicing Printing First page line items blank

Hi Everybody,
Customer Invoicing Printing First page line items blank and it is printing it from the second page. Please help me on this.
Regards,
Md Ziauddin.

item No Material No Descripition Putaway Bin SUT Vendor Batch LE QTY COA Base UOM
this how my line item should like, i am able to print only single line item for each item no.
if i have 5 pallets for single line item, i want the same line item to be printed 5 times and this is what i am looking at

Logistics invoice print out

Hi,
Soon the invoice got parked, client need printout of that invoice. May i know, which is the appropriate 'out put type" we need to include in condition records?, is it "INS" or "LIEF" or "REKL"
Regards,
Sattuj

we are moving into SAP to reduce all the paper work.. moreover you have hard copy of the vendor Invoice and the super ordinate have the access to SAP.
So the process would sub ordinate checks all the invoice in SAP and park... and his boss can verify again and post the parked Invoice in SAP if they need more verifications.. this is standard SAP best practise... we also can configure workflow to inform when the invoice is parked and it triggers a mail to his boss...
But printing parked invoice or Invoice is not useful. it just creates overhead..
for more Invoice workflow information
[http://help.sap.com/saphelp_46c/helpdata/es/26/098ba835e1d311ba4d0800060d888b/content.htm]

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

Incoming invoice printing

Hi All,
we want to make the setting for printing voucher for all incoming out going payments and bank payments.in standard SAP at the time of document generating.
KIndly explain the requird setting how to make it in SAP
Thanks in advance,
Regards,
Jyothi

Hi Jothi,
Kash is right, you have to develope a Z transaction for printing voucher.
In our company we are currently using Z repor pasted below to print the vouchers based on the doucment type. See if this suits your need. (Copy and past this program and consult your abaper)
Regards
Naveen
**& Report ZFI_VOUCHER*
*REPORT ZFI_UAE_RPT_JVO_NEW.*
**--table declarartion*
*TABLES : BKPF,*
 *BSEG,*
 *SKAT,*
 *BSIS.*
**--data declarartion*
*DATA: V_TYPE TYPE STRING,*
 *V_TYPE_DES TYPE STRING,*
 *V_NAME LIKE KNA1-NAME1.*
**--internal table declarartion*
*DATA : IT_BKPF LIKE STANDARD TABLE OF ZIT_BKPF WITH HEADER LINE.*
*DATA : IT_BSIS LIKE STANDARD TABLE OF ZIT_BSIS WITH HEADER LINE.*
*DATA : IT_BSEG LIKE STANDARD TABLE OF BSEG WITH HEADER LINE.*
**--selection-screen*
*SELECTION-SCREEN BEGIN OF BLOCK BLK1 WITH FRAME TITLE TEXT-T01.*
*SELECT-OPTIONS : P_BELNR FOR BSEG-BELNR OBLIGATORY.*
*PARAMETERS : P_GJAHR LIKE BKPF-GJAHR OBLIGATORY.*
**----change*
*PARAMETERS : P_BLART LIKE BSIS-BLART OBLIGATORY.*
*PARAMETERS : P_BUKRS LIKE BKPF-BUKRS OBLIGATORY.*
*PARAMETERS : P_PRCTR LIKE BSIS-PRCTR.*
*SELECTION-SCREEN END OF BLOCK BLK1.*
**--at selection-screen*
*AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_BELNR-LOW.*
**--possible values for Document number*
*PERFORM POV_DOCUMENT_NO.*
*AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_BELNR-HIGH.*
**--possible values for Document number*
*PERFORM POV_DOCUMENT_NO.*
**--start of selection*
*START-OF-SELECTION.*
**--getting header data*
*PERFORM FETCH_HEADER_DATA.*
**--getting item text*
*PERFORM GET_TEXT.*
**--getting item data*
PERFORM get_item_data.**
**--format internal table*
*PERFORM FORMAT_IT.*
**--end of selection*
*END-OF-SELECTION.*
**--Find doc type*
*PERFORM ASSIGN_DO_TYPE.*
**--call smart form*
*PERFORM CALL_SMARTFORM.*
**& Form fetch_header_data*
 getting header data**
*FORM FETCH_HEADER_DATA .*
*SELECT BELNR*
 *BUKRS*
 *GJAHR*
 *BLDAT*
 *BUDAT*
 *MONAT*
 *WAERS*
 *XBLNR*
 *FROM BKPF*
 *INTO TABLE IT_BKPF*
 *WHERE BELNR IN P_BELNR*
 *AND GJAHR EQ P_GJAHR*
 *AND BLART EQ P_BLART*
 *AND BUKRS EQ P_BUKRS.*
*IF SY-SUBRC NE 0.*
 *MESSAGE 'Data not found for the given condition' TYPE 'E'.*
*ENDIF.*
*ENDFORM. " fetch_header_data*
**& Form get_text*
 getting item text**
*FORM GET_TEXT .*
*DATA: V_LIFNR TYPE LFA1-LIFNR,*
 *V_KUNNR TYPE KNA1-KUNNR,*
 *V_BLART LIKE BKPF-BLART,*
 *V1 TYPE I.*
*SELECT SINGLE BLART*
 *INTO V_BLART*
 *FROM BKPF*
 *WHERE BELNR IN P_BELNR*
 *AND GJAHR EQ P_GJAHR*
 *AND BLART EQ P_BLART*
 *AND BUKRS EQ P_BUKRS.*
*SELECT BELNR*
 *LIFNR*
 *KUNNR*
 *HKONT*
 *DMBTR*
 *SHKZG*
 *PRCTR*
 *KOSTL*
 *SGTXT*
 *INTO CORRESPONDING FIELDS OF TABLE IT_BSEG*
 *FROM BSEG*
 *WHERE BSEG~BELNR IN P_BELNR*
 *AND GJAHR EQ P_GJAHR*
 *AND BUKRS EQ P_BUKRS.*
*LOOP AT IT_BSEG.*
 *V1 = IT_BSEG-HKONT.*
 *IF IT_BSEG-LIFNR IS NOT INITIAL AND ( V1 BETWEEN 105005700 AND 105006700 )*
 *OR V1 = 208001500*
 *OR V1 = 208000100.*
 *IF SY-SUBRC = 0.*
 *CLEAR V_NAME.*
 *SELECT SINGLE NAME1*
 *FROM LFA1*
 *INTO V_NAME*
 *WHERE LIFNR EQ IT_BSEG-LIFNR.*
 *IT_BSIS-HKONT = IT_BSEG-LIFNR.*
 *IT_BSIS-TXT20 = V_NAME.*
 *PERFORM FILL_IT_BSIS.*
 *ENDIF.*
 *ELSEIF IT_BSEG-KUNNR IS NOT INITIAL AND ( ( V1 BETWEEN 206000100 AND 206000140 )*
 *OR ( V1 BETWEEN 105000900 AND 105001200 ) ).*
 *IF SY-SUBRC = 0.*
 *CLEAR V_NAME.*
 *SELECT SINGLE NAME1*
 *FROM KNA1*
 *INTO V_NAME*
 *WHERE KUNNR EQ IT_BSEG-KUNNR.*
 *IT_BSIS-HKONT = IT_BSEG-KUNNR.*
 *IT_BSIS-TXT20 = V_NAME.*
 *PERFORM FILL_IT_BSIS.*
 *ENDIF.*
 *ELSE.*
 *SELECT SINGLE TXT20*
 *FROM SKAT*
 *INTO IT_BSIS-TXT20*
 *WHERE SKAT~SAKNR EQ IT_BSEG-HKONT.*
 *IT_BSIS-HKONT = IT_BSEG-HKONT.*
 *PERFORM FILL_IT_BSIS.*
 *ENDIF.*
 *APPEND IT_BSIS.*
*ENDLOOP.*
*ENDFORM. " get_text*
**& Form format_it*
 text**
*FORM FORMAT_IT .*
*LOOP AT IT_BSIS.*
 *IF IT_BSIS-SHKZG EQ 'S'.*
 *IT_BSIS-DEBIT = IT_BSIS-WRBTR.*
 *ELSE.*
 *IT_BSIS-CREDIT = IT_BSIS-WRBTR.*
 *ENDIF.*
 *MODIFY IT_BSIS .*
*ENDLOOP.*
*CLEAR: IT_BSIS.*
*ENDFORM. " format_it*
**& Form call_smartform*
 text**
*FORM CALL_SMARTFORM .*
*DATA: FORMNAME TYPE TDSFNAME VALUE 'ZFI_VOUCHER_PRINT'.*
*DATA: FM_NAME TYPE RS38L_FNAM.*
*CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'*
 *EXPORTING*
 *FORMNAME = FORMNAME*
 *IMPORTING*
 *FM_NAME = FM_NAME.*
*DATA: V_PRCTR LIKE BSIS-PRCTR.*
*CALL FUNCTION FM_NAME*
 *EXPORTING*
 *V_TYPE_DES = V_TYPE_DES*
 *TABLES*
 *IT_BKPF = IT_BKPF*
 *IT_BSIS = IT_BSIS*
 *EXCEPTIONS*
 *FORMATTING_ERROR = 1*
 *INTERNAL_ERROR = 2*
 *SEND_ERROR = 3*
 *USER_CANCELED = 4*
 *OTHERS = 5.*
*IF SY-SUBRC <> 0.*
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO**
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.**
*ENDIF.*
*ENDFORM. " call_smartform*
**& Form assign_do_type*
 text**
*FORM ASSIGN_DO_TYPE .*
*V_TYPE = P_BLART.*
*CASE V_TYPE.*
 *WHEN 'AB'.*
 *V_TYPE_DES = 'CASH VOUCHER'.*
 *WHEN 'SA'.*
 *V_TYPE_DES = 'JOURNAL VOUCHER'.*
 *WHEN 'KZ'.*
 *V_TYPE_DES = 'VENDOR PAYMENT'.*
 *WHEN 'KA'.*
 *V_TYPE_DES = 'VENDOR PAYMENT-CASH'.*
 *WHEN 'DZ'.*
 *V_TYPE_DES = 'CUSTOMER PAYMENT'.*
 *WHEN 'KG'.*
 *V_TYPE_DES = 'VENDOR CREDIT NOTE'.*
 *WHEN 'DG'.*
 *V_TYPE_DES = 'CUSTOMER DEBIT NOTE'.*
 *WHEN 'KR' OR 'RE'.*
 *V_TYPE_DES = 'VENDOR INVOICE'.*
 *WHEN 'RV' OR 'DR'.*
 *V_TYPE_DES = 'CUSTOMER INVOICE'.*
*ENDCASE.*
*ENDFORM. " assign_do_type*
**& Form fill_it_bsis*
*FORM FILL_IT_BSIS .*
*IT_BSIS-BELNR = IT_BSEG-BELNR.*
*IT_BSIS-WRBTR = IT_BSEG-DMBTR.*
*IT_BSIS-PRCTR = IT_BSEG-PRCTR.*
*IT_BSIS-SHKZG = IT_BSEG-SHKZG.*
*IT_BSIS-KOSTL = IT_BSEG-KOSTL.*
*IT_BSIS-SGTXT = IT_BSEG-SGTXT.*
*ENDFORM. " fill_it_bsis*
**& Form pov_document_no*
 possible values for Document number**
*FORM POV_DOCUMENT_NO .*
*DATA: BEGIN OF L_BKPF,*
 *BKTXT TYPE BKPF-BKTXT,*
 *GJAHR TYPE BKPF-BELNR,*
 *BLART TYPE BKPF-BLART,*
 *BELNR TYPE BKPF-BELNR,*
 *END OF L_BKPF.*
*DATA : IT_L_BKPF LIKE STANDARD TABLE OF L_BKPF WITH HEADER LINE.*
*SELECT BKTXT*
 *GJAHR*
 *BLART*
 *BELNR*
 *INTO TABLE IT_L_BKPF*
 *FROM BKPF.*
*CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'*
 *EXPORTING*
 *RETFIELD = 'belnr'*
 *DYNPPROG = SY-REPID*
 *DYNPNR = SY-DYNNR*
 *DYNPROFIELD = 'P_BELNR '*
 *VALUE_ORG = 'S'*
 *TABLES*
 *VALUE_TAB = IT_L_BKPF.*
*IF SY-SUBRC <> 0.*
*ENDIF.*
*ENDFORM. " pov_document_no*
Edited by: Naveen Singh on Aug 23, 2009 3:57 PM
Edited by: Naveen Singh on Aug 23, 2009 4:07 PM

Vendor invoice print

Similar Messages

Maybe you are looking for