PO invoice completed

All,
Whether there is any field where I can see the PO is finally invoiced ?
For eg an Import PO is created for 5000 qty .
Clearing agent with separate vendor code is included in the conditions of customs and freight for this PO .
2500 qty goods received against this PO and invoiced for main vendor and clearing agent vendor . Now there will be any indicator automatically where it says invoice completed for this particular qty ?
Kindly advise.
regards

Hi,
In MIRO transaction, the PO item you can set the final invoice indiator. Read the SAP help for this field. Check if this is what you are looking for.
======================
Final invoice indicator
Indicates that the last invoice from a vendor has been received for an item and/or that no further invoice is expected.
Use
The final invoice indicator serves as information for the applications
Cash Management and Forecast
Cash Budget Management
Funds Management
If you set the final invoice indicator, purchase order commitments are reset.
However, the final invoice indicator does not prevent further invoices from being posted. Furthermore, it does not replace GR/IR account maintenance in the event of a variance between GR quantity and invoice quantity.
Examples
Purchase order: 100 pieces of material A at $10/piece
-> The PO commitment is automatically set to $1000.
Goods receipt: 80 pieces
Invoice for 60 pieces = $600
-> The purchase order commitment is automatically set to $400.
Invoice for 15 pieces = $150 - final invoice indicator set.
-> The purchase order commitment is automatically set to zero.
Since the final invoice indicator does not have any effect on the GR/IR clearing account, you must clear the difference of 5 pieces ($50) on the GR/IR clearing account if no further invoices are posted.
========================
Regards,
Siva

Similar Messages

  • Authorisation object for Park Invoice & Complete

    Hi Friends,
    In our Business we have different persons for Park Logistics Invoice verification(LIV)  & Complete LIV for perfomaing the transactions. For both the activities T.Code is MIR7.
    Can we assign to differnet persons parking & completion of LIV. If so can any body tell the object name for the same. I tried by going to SU24, in that I couldn't find the suitable one.
    Our scenarios is while making the LIV goods receipt didn't took place, so we park the invoice. After completing goods receipt we will complete the LIV with PO no / Delivery note.
    Thanks in advance.
    Regards
    Sai Krishna

    Hi Charlie,
    Thank u for ur response.
    Actually there are three levels of LIV authorisations required as mentione dbelow:
    1. For Parking
    2. For Completion
    3. For Posting.
    For Posting I am using MIRO. For that reason I am looking for authorisation of Parking & Completion different authorisations.
    I hope now it might be clear to u.
    Regards
    Sai Krishna

  • After invoice completed the sales order is showing being processed

    Dear All,
    I have created one Sales Order.  Checked the incomplet procedure where it gives document is completed.
    I have created invoice with reference to this Sales Order.  Invoice is successfully created and Accounting document is also generated.
    Now if I check the document flow the Sales Order is showing as Being Process (not completed)
    Can anyone tell me the reason why this sales order is showing Being process in Document Flow though the invoice is completly processed.
    with regards
    Amjathpasha

    Hi,
    Please check the below link. All this is happening because of some inconsistency in the system, for which we do not have a clear reason, every time and every issue may be having a different reasons. It is advisable to go through the different solutions provided by others in the forum and analyze which is suitable for your scenario.
    Hope below link helps you...
    Re: Sales Order Status
    Venkat Cheedalla

  • INCIAP Create Intercompany AP Invoices-Completes in Error

    Hi to all,
    We ran the following intercompany request:  "Create Intercompany AP Invoices".  In reviewing the logfile the tail end of the file has the following info:
    Get if OM is installed
    Getting the Sales Order Information
    Getting the Inventory Organization from Item Validation Organization.
    l_IC_INVENTORY_ORGANIZATION_ID is 1
    Call inv_workflow.call_generate_cogs
    l_gl_ccid is 132972
    global->invInfo.ap.ccid is 132972
        In inliap.lpc, inapcil()
    Creating invoice line    Last row processing.
        In inlico.lpc, inilcbk()
    End of Processing Inovice Line ID: 191190206.000000
    Invoice Line ID: 191190206.000000 Status: SUCCESS
    Loading global info structure
    Processing invoice line, ID = 68435560
    In inciap.opc, processInvoiceLine()
    Get if OM is installed
    Getting the Sales Order Information
    Getting the Inventory Organization from Item Validation Organization.
    l_IC_INVENTORY_ORGANIZATION_ID is 1
    Call inv_workflow.call_generate_cogs
    l_gl_ccid is 132994
    API inv_workflow.call_generate_cogs returned failure./PROD/shared/apps/apps_st/appl/inv/12.0.0/bin/INCIAP
    Program was terminated by signal 11
    We've located the sales order and reviewed the transaction type COGS.  The COGs is valid. Since the last lines state CCID: 132994 is this the root cause? We have checked the CCID and it is enabled.  How do we find which line is giving the issue?  And is the COGs the root cause or something else?
    Thanks

    Hi,
    This concurrent programs log is very limited to conclude the issue, please try to rerun the same program and get the FND log, steps pasted below:
    1) Go to the System Profile options and set the following parameters:   
        FND: Debug Log Enabled = YES
        FND: Debug Log Filename = NULL
        FND: Debug Log Level STATEMENT (most detailed log)
        FND: Debug Log Module %
    2) run your concurrent program
    3).
    SELECT LOG.LOG_SEQUENCE, LOG.message_text message
    FROM FND_LOG_MESSAGES LOG,
    FND_LOG_TRANSACTION_CONTEXT CON
    WHERE CON.TRANSACTION_ID = <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<Your Concurrent request ID>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    AND CON.TRANSACTION_TYPE = 'REQUEST'
    AND CON.TRANSACTION_CONTEXT_ID = LOG.TRANSACTION_CONTEXT_ID
    ORDER BY LOG.LOG_SEQUENCE ;
    Hope it helps!
    Regards,
    Yuvaraj

  • 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                  

  • Posting of cancelled Invoice after posting date is over

    Hello Experts,
    I am stuck up with a situation and as such seek your help.
    A invoice was generated and the subsequent accounting document was also cleared. Now after the posting date was over, someone cancelled the invoice by T.code VF11 and as expected it didnt get posted .The document flow showing is as per below :
    Order - open
    Invoice - completed
    Accounting Document - Cleared
    Cancel Invoice - Open
    Now, the business and their audit policies do not allow the client to cancel the invoice in back date ( within the posting period).
    What are the options do we have to tackle the situation.
    Joy

    The issue has been temporarily addressed by changing the posting date.
    However, now the client wants us to make an ABAP development so that no user is able to cancel the invoice after posting date is over. Now for that I have the following issues. Can someone please help me out in this.
    The basic process details I am following is as per below:
    For Transaction Code VF11 (i.e for Cancellation of Invoice) , when the invoice number which is subject to cancellation is provided, the System should search in VBRK table for the following :-
    1)The System will at first search whether the entry exists or not. If the Entry is not valid then it should give an message u201C Document xxxxx does not Existu201D.This is in line to the existing practice.
    2) If the Document number is valid then it will go to the billing date field and  will fetch the value from the VBRK table . Then it will match  whether the value fetched (i.e. this Invoice date)  is in present posting period or not. The system can find the posting period from the table V_T001B.
    a.If  the  Invoice date lies in the present posting period then the system will allow the cancellation document to be saved. This is in line to the existing process.
    b.If the Invoice date lies beyond the present posting period then the system will not allow to save the cancellation of the Invoice with a pop up message of u201C The Document number subject to cancellation do not lie within the present posting periodu201D .
    Now We have looked both the tables, from VBRK we will get Doc# and Billing date(FKDAT) but when we select Posting Date from table T001B( Permitted Posting Periods) there is some issue.
    1.  What will be the condition for selecting records from T001B table.Since there is multiple key fields
        RRCTY (Record Type) ,
        BUKRS (Posting Period Variant) ,
        MKOAR (Account Type or Masking)
        BKONT (To Account). 
    So, to get unique record what will be the value of this key fields. Is there any relationship with VBRK table ? 
    2.  Which field I have to consider as Posting Date or Period. Because there are many fields related to Posting period.

  • How to reverse PGI @ VL09 for delivery with subsequent invoice

    Greetings
    Our business process sometimes requires billing to happen prior to PGI.
    Hence, we have modified copy control settings to allow billing based off delivery creation (rather than PGI delivery).
    No modifications to the item categories and we are using standard movement types 601/602
    My issue is at VL09.
    VL09 will not allow me to reverse without cancelling the billing document.
    I get a message No data available for these selection criteria
    I have checked OMJJ movement type settings and I dont see anything here.
    Can anyone point me in the right direction to customize such a setting if it exists?
    We are using ECC 6.0
    thank you
    Ken

    hi
    your issue as standard behavior , when delivery document  billing status completed ,  you can not do the PGI , when you cancel the billing document then only system will accept PGI ,
    when you cancel the billing document , delivery document billing status will change , so accept PGI
    this status comes based on billing document types , like final billing (f2) delivery billing status comes complete, proforma invoice completed then delivery billing status comes not yet proceed
    this is the why system not accept the PGI for final billing document done
    check proforma billing document delivery PGI
    Regards
    sankar

  • Restrict excise invoice from proforma invoice after reverse PGI

    Hello experts,
    Our sales flow is stock transfer order-> Fast Delivery-> PGI -> Billing (jex)--> excise invoice
    If we have to reverse the PGI first .System give error (cancel excise invoice first)after cancel excise invoice reverse pgi then cancel proforma invoice (complete).
    But once Again excise invoice  allows me create from cancel billing document.
    My requirement is I want to  restrict excise invoice from billing document which already cancel and reverse post good issue.
    Thanks

    HI G. Lakshmipathi,
    I have checked configuration it same as you suggested.
    I have compared  ABAP code in report MJ1IINI01 with other system ,
    there is code to check the cancellation of proforma invoice
    *Check if proforma is cancelled (Billing type is JEX & VBRK-VBTYP = 'U')
    *For proforma,VBRK-FKSTO is not set as X,but VBRK-RFBSK will be set as E
    IF WA_VBRK-VBTYP = 'U' and WA_VBRK-RFBSK = 'E'.
         MESSAGE e264(8i) WITH j1ii100-vbeln.
       ENDIF.
    But in my system its not shown .
    So how can i activate this message is there any setting in IMG to activate message .

  • Accounting document from _cancel invoice "Not cleared"

    Dear All,
    When we create a billing document then an accounting document gets created automatically in the background and then when we cancel the billing document then another accounting document gets generated and the entries in the previous accounting document are offset and the status of both the document becomes cleared. But in my case after the cancel billing document has been generated only the accounting document of the invoice is getting cleared but the accounting document of the cancel billing document is NOT CLEARED. Can anybody please help me find out a solution to the issue.
    Flow chart:
    Sales order = completed
    Delivery = completed
    Goods Issue = complete
    Invoice = completed
    Accounting Document = cleared
    Cancel Invoice (S1) = Completed
    Accounting Document = Not Cleared
    In customer line item still showing the cancel accounting document.
    When I go to VFX3 and try to release the cancel invoice i get the message-" no documents found for these selection criteria."
    Please help me  to find a solution.
    Thanks and B/R
    Bishnu

    closed
    Develop the courtesy to update the forum if your problem is solved so that it will be helpful to others who also faced similar issue.  By doing so, you can show that you respect members who have spent time to respond to your issue.
    thanks
    G. Lakshmipathi

  • Incomimg Payment / AR invoice B1 2005 Question

    I have an issue with and Incoming Payment in B1 2005
    I appled a check to 2 invoices.  First Invoice had a Credit Memo applied to part of the balance.  The check was for the remaing balance on the forst invoice plus the total of the second invoice.  When viewing the forst Invoice,  the Invoice shows closed in the status field,  with total amout applied the same as the inoivce total.  On the Customer's AR inquiry screen,  the first invoice show it is closed.  The second invoice when viewed,  shows closed with the amout applied the same as the balance.  But on the Customer's AR screen,  the Invoice shows the invoice open for the full amount.   When I go into Incoming Payments for the Customer is question,  in a greyed out box just to the left of the box that shows the amount of the invoices selected for payment,  the amount of the second invoice is deiplayed in that box.  If I check the On Account check box,  the amount is then displayed in the box of the amount to be distributed.   Has anyone seen this before?  If I goe into Automatic reconcillations,  the Invoice shows open but the Payment is no where to be seen.  I was hoping in one of the various reconcilations that I would be able to apply the amout to the Invoice,  but only the Invoice is displayed as open. 
    Does anyone have any idea on how to close the Invoice COMPLETELY?  And also what does the Amount in the Box to the left of the ORCT.NoDocSUm field represent and how to I apply or get ride of the amount?
    Thanks in advance for any input!
    Dana

    Hi Michelle ,
    Your invoice might not have closed because of rounding issues or
    i have found one issue at delivery before :
    1.If your freight code donot match between delivey and invoice , it doesn;t get closed .
    It could be one of the issue might be happening ..
    Otherwise log a support to SAP for further analysis ..
    Thank you
    Bishal

  • AR DATA FLOW (TABLE LEVEL) - INVOICE편

    제품 : FIN_AR
    작성날짜 : 2003-09-16
    AR DATA FLOW (TABLE LEVEL) - INVOICE편
    =====================================
    PURPOSE
    이 문서에서는 AR table들에 대해 어떻게 data가 들어가는지에 대해
    설명한다.
    Invoice transaction을 기준으로 설명한다.
    Explanation
    1. Invoice
    User가 invoice를 입력하면, 아래의 table들에 data가 insert된다.
    o RA_CUSTOMER_TRX_ALL (Invoice Header)
    o RA_CUSTOMER_TRX_LINES_ALL (Line Details)
    o RA_CUST_TRX_LINE_GL_DIST_ALL (Information for posting to GL)
    o RA_CUST_TRX_LINES_SALESREPS_ALL (Sales Credit Information)
    일단, invoice가 "Complete"되면, 아래의 table에 한줄(혹은 그 이상)이
    추가로 Insert된다.
    o AR_PAYMENT_SCHEDULES_ALL (Running Totals for Invoice Amounts)
    대체로 하나의 invoice는 하나의 Payment schedule record를 가지지만,
    만약 할부(Installment)로 Pay처리되는 invoice라면, installment하나당
    하나의 Payment schedule record를 가진다.
    | | /| |
    | TRX |---------------<-| PAYMENT |
    | | \| SCHEDULE |
    | |
    | |
    ^ -------
    /|\ |
    ------------ |
    | | |
    | TRX_LINES | |
    _| | |
    / ------------ |
    | | | |
    \__/ | |
    ^ |
    /|\ |
    | |
    | GL_DIST |
    | |
    1.1 RA_CUSTOMER_TRX_ALL
    Invoice의 Header정보(Customer, Invoice Number, date.. etc)를 담고 있는 table이다.
    Invoice하나당 한줄의 정보가 Insert된다.
    Key = CUSTOMER_TRX_ID (generated from sequence RA_CUSTOMER_TRX_S)
    Important Fields
    TRX_NUMBER - User Entered Invoice Number
    CUST_TRX_TYPE_ID - Foreign key to RA_CUST_TRX_TYPES
    BILL_TO_CUSTOMER_ID - Foreign Key to RA_CUSTOMERS
    SHIP_TO_CUSTOMER_ID - Foreign key to RA_CUSTOMERS
    TRX_DATE - Invoice Date
    COMPLETE_FLAG - Y or N
    1.2 RA_CUSTOMER_TRX_LINES_ALL
    Invoice의 Line정보(수금 item및 금액, Tax등)가 insert되는 table이다.
    Invoice하나당 한줄이상을 가진다.
    Key = RA_CUSTOMER_TRX_LINE_ID (from sequence RA_CUSTOMER_TRX_LINES_S)
    Important Fields
    CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
    LINE_TYPE - LINE, TAX, FREIGHT
    QUANTITY_INVOICED - Line Quantity
    UNIT_SELLING_PRICE - Price per unit
    EXTENDED_AMOUNT - Quantity * Price
    LINK_TO_CUST_TRX_LINE_ID - Null for LINE, for TAX and FREIGHT lines
    contains the RA_CUSTOMER_TRX_LINE_ID of
    associated LINE record
    1.3 RA_CUST_TRX_LINE_GL_DIST_ALL
    GL로 Posting될 정보가 담겨져 있다.
    Invoice Line당 한줄 + Invoice Header 한줄로 이루어져 있다.
    (예를들어, Invoice의 Line이 총 3줄이라면, RA_CUST_TRX_LINE_GL_DIST_ALL table에는 총 4줄의 정보가 담기게 된다.)
    Key = CUST_TRX_LINE_GL_DIST_ID (from sequence)
    Important Fields
    CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
    CUSTOMER_TRX_LINE_ID - Foreign key to RA_CUSTOMER_TRX_LINES or
    Null if this relates to Invoice Header.
    AMOUNT - Value of distribution - entered currency
    ACCOUNTED_AMOUNT - Value of distribution - book currency
    CODE_COMBINATION_ID - Foreign key to GL_CODE_COMBINATIONS
    POSTING_CONTROL_ID - -3 if unposted
    GL_DATE - Accounting date.
    GL_POSTED_DATE - Date Invoice posted to GL.
    1.4 RA_CUST_TRX_LINE_SALESREPS_ALL
    해당 invoice가 입력될때 함께 입력된 Sales Person에 대한 정보가
    담겨져 있다.
    1.5 AR_PAYMENT_SCHEDULES_ALL
    해당 invoice에 대해서 Line, Tax, 운송비 등 각각의 항목에 대한 Total값과
    Remaining값을 담고 있다.
    대체로 Invoice당 한줄이 insert된다.
    Key = PAYMENT_SCHEDULE_ID (from sequence AR_PAYMENT_SCHEDULES_S)
    Important Fields
    CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
    STATUS - (OP)en or (CL)losed
    ACTUAL_DATE_CLOSED - 31-DEC-4712 if still open, otherwise
    date payment schedule closed.
    GL_DATE_CLOSED - 31-DEC-4712 if still open, otherwise the
    gl date of the closing transaction.
    AMOUNT_DUE_ORIGINAL - Invoice Total Amount
    AMOUNT_DUE_REMAINING - Total Amount outstanding for Invoice.
    AMOUNT_LINE_ITEMS_ORIGINAL - Sum of Invoice Line amounts.
    AMOUNT_LINE_ITEMS_REMAINING - Outstanding Line amounts.
    TAX_ORIGINAL - Total Tax for Invoice.
    TAX_REMAINING - Outstanding Tax for Invoice
    FREIGHT_ORIGINAL - Total Freight For Invoice
    FREIGHT_REMAINING - Outstanding Freight
    AMOUNT_APPLIED - Total payments applied to this Invoice.
    AMOUNT_CREDITED - Total Credit Memos applied.
    AMOUNT_ADJUSTED - Total value of adjustments.
    The payment schedule should balance within itself, ie the following
    calculations
    should be true:-
    AMOUNT_DUE_ORIGINAL = AMOUNT_LINE_ITEMS_ORIGINAL
    + TAX_ORIGINAL
    + FREIGHT_ORIGINAL
    AMOUNT_DUE_REMAINING = AMOUNT_LINE_ITEMS_REMAINING
    + TAX_REMAINING
    + FREIGHT_REMAINING
    AMOUNT_DUE_ORIGINAL = AMOUNT_DUE_REMAINING
    + AMOUNT_APPLIED
    - AMOUNT_CREDITED
    + AMOUNT_ADJUSTED
    Reference Documents
    Note : 29277.1

    Hello,
    The basic flow of data is
    ERP tables - source snapshots - source views (eg MRP_AP%) - staging tables (MSC_ST%) - ODS tables ( MSC%)
    Check out note 412375.1. This is the flow for sales order data for ASCP.
    regards
    Geert

  • AR Invoice Flat Files For Customers

    Hi All,
    There's a requirement to provide a data file with outstanding AR invoice to one of our customers.
    In this we are goning to develop a program to extract the relevant outstanding invoices.However we are going to have the following controls as well.
    01) Allow the user to extract the invoices an may times they want till they upload the file to customer's suystem
    02) To allow that facility we are going to define a process called draft extraction and a final extraction.
    03) Once a file has been successfully uplaoded they should confirm that the batch has been uploaded successfully
    04) If a batch has been confirmed as successful users cannot extract the invoices again. If they want to do it they need to clear the values populated in the DFF which are anables for this purpose.
    05) If a batch has been generated in final mode it must be confirmed prior to generating a new file. Otherwise no output will be generated.
    My question is normally what are the other types of controls that you implement in these type of scenarios.
    and what sort of information do we need to capture in our side in the extractions.
    Thanks,

    Hi:
    Few inputs -
    1. I hope you would extract based on invoice 'complete' status but you may need to include the logic to make sure no change happens on the invoice after your final extract. (Ex user can incomplete the invoice, make some change and again complete it)
    2. You may also include some reconciliation mechanism such as # of invoice count and amount extracted = # of invoice count and amount in flat file.You can use staging tables information to do this reconciliation.
    Hope this is useful.
    Tarun

  • Std Work flow for Invoice Parking & posting

    I am working om std SAP workflow for invoice document parking :
    I have done the following activities :
    1. Activate Work flow Template for Document Completion
    Here i activated the event "Complete the Parked Log. IV Document"--> Incoming Invoice Document Parked. It is showing a green traffic light .
    In agent assignment
    Complete the Parked Log. IV Document>Complete the Parked Log. IV Document>Complete the Parked Invoice--> i have assigned the user MMCONFIG
    2. In Define Release Criteria i have the following settings :
    1000 H Credit 0.01 INR US MMCONFIG
    1000 S Debit 0.01 INR US MMCONFIG
    3. In Activate Workflow Template for Release for Posting
    Here i activated the event Incoming Invoice Complete: ReleaseRel & i m getting a green traffic light .
    In assign agents i did the following
    Release the Completed Log. IV Document>Release the Completed Log. IV Document>Release the Completed Log. IV Document i assigned the user MMCONFIG
    In Invoice Parking: Approve Release i assigned the user MMCONFIG .
    For Invoice Parking: Release Invoice
    Invoice Parking: Posting an Invoice " I AM NOT ABLE TO ASSIGN ANY USER AS THESE ARE BACKGROUND TASKS ".
    Now when do a MIR7 - Park invoice & save the invoice as complete i am getting a mail in the mail box of MMCONFIG saying :
    "Invoice Release 5105xxxxxxx 2009, Completed by MMCONFIG "
    I go & release the same invoice .
    Then i executed MIRO & tried posting the released invoice . The sysem doesnt allow me 2 post the invoice .
    It automatically goes to MIR4 transaction & forces me to save as complete
    if i try to post it the system says "Parked document is release-relevant and cannot be posted"
    Pls tell me how can I post the invoice & IF MY SETTINGS FOR THE WORKFLOW IS OK ???
    Regards
    Anis

    Firstly,  check with the Binding of the event and workflow, if they are fine
    then check if the workflow gets triggered when you are posting... to check this,
    First go to transaction SWU8 - turn on the workflow trace and then
    Proceed with posting the invoice
    go to transaction SWU8 again and then turn off the workflow trace
    go to SWU9 - to check which all workflows got triggered....
    If there is any workitem in your workflow, then go to SWI1 and select the workitem of that workflow and press shift+F8 to check the status of it and also check to which all agents it had sent...
    If possible just give a hardcoded value in the workitem for testing purpose and check if that goes properly, later on implement the rule.....
    If the workflow does not triggere - go to transaction SWETYPV and deactivate and activate the event linkage with that workflow....
    Regards,

  • "Delivery Status" in SO is "Partially delivered" though complete PGI hppnd.

    Dear Friends
    An SO has been created  (single line item), delivered & invoiced completely.
    The issue is at "Delivery status"  & "overall status"field in SO (both header & item level).
    Though complete delivery & PGI has been completed & also invoiced., the 'Delivery status' in SO is showing "Partially delivered"
    & 'overall status" as "Being processed".
    But at S.Line cat level (CP)  of SO, the system is showing the correct delivered qty.
    In delivery, the GI status is C (Completed). (both at header & item)
    The  item is a batch split item. At So, item cat is TAN. In delivery, at batch split level, it is ZTAN
    I've checked in all places, do NOT understand why this behavior at SO "delivery status" & 'overall status" field.
    Rgds
    Sumanth.G.

    Hello,
    Check the status of the sales order both Header and item.
    Go to the sales order (dont select any line item)  Environment --> Status overview, the system will show the header ans well as the list of line items. Check the individula line items, it will show order qty, Dly Qty, Delivered Qty and invoice Qty. Try to analyse from here...
    Regards,
    SAM

  • Cancellation of Proforma Invoice

    Hello All,
    I am looking out for a solution in standard SAP and scenario is as below:-
    1. I create a sales order
    2. Then I create a Proforma Invoice against this sales order.
    3. When I see the document flow once a create the Proforma, I can see two statuses - Invoice:Completed, Sales order: Open
    4. Now, if I want to make any changes in the sales order, system doesn't allow me to do so even if I have cancelled the proforma invoice by putting the status 'Complete' in VF02 initial entry screen.It throws an errro ' item 000010 cannot be deleted because of subsequent document xxxxxxxx' which is quite right.
    5. Then I have changed in VOFA setting for F5 billng type such as - I have put 'S1' cancellation billint type in F5 (which is always blank) with an assumption that system will allow me to do VF11 for this F5 invoice.
    6. Even after step 5, system doen's allow me to do VF11 and throws an errro ' Proforma invoice can't be cancelled'
    My ultimate requirement is - I should be able to do VF11 for F5 which will update the document flow in a proper way and put the sales order in editable mode which is not happening at this moment.
    I would appreciate your valuable inputs on the same.
    Regards,
    Hrishi

    Hi,
    The only and easiest way is to assign the reason for rejection for your sales document.
    If there are huge number of order,then you can go for mass updation using the T.Code "MASS".
    Goto the T.Code "MASS".
    Enter the object type as "BUS2032".
    Execute.
    Click on "Fields" tab.
    Click on "Find".
    Enter the search term as "MASSVBAP-ABGRU".Identify that entry and then select that line.
    Execute.
    Enter your sales orders number range.Maintain the rejection reason.So that the status will be changed.
    Regards,
    Krishna.

Maybe you are looking for