Migration object for Aggregated Invoice

Hi Experts,
Just wanted to know if there is any object to migrate Aggregated Invoice in deregulated market scenario in a distributor's system which updates field DFKKTHI-BCBLN.
We are able to migrate the open individual invoices of final customers as well as open aggregated invoice of the suppliers separately. But, we are unable to update the field Document Number of Posting to Service Provider Account (DFKKTHI-BCBLN) at the time migrating the aggregated invoice.
Unless we establish the link between the individual invoice & aggregated invoice in table DFKKTHI it will be difficult to process these open documents further for payment and posting of distribution lot.
If anyone has come across this situation please let us know if there is any migration object by which we can establish the link between the individual invoice & aggregated invoice in table DFKKTHI.
Please advice
Thanks & Regards
Satyajeet

Dear Naval Bhatt,
The business objects:
'BUS1055' - Accounts payable ledger
The business object Accounts payable ledger is ledger that is defined for the representation of accounting transactions with creditors.
It records values at company code level.
'BUS3008' - Accounts payable account
The business object Accounts payable document is an accounting document that contains records on value movements in a company code that are relevant to accounts payable accounting.
Reward points if this is helpful. Close the thread if your query is resolved.
Regards,
Naveen.

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

Business object for AP invoice transaction FB60

hi all,
Which business Object is triggered when we AP invoice is created
transaction FB60
thanks in advance
Naval Bhatt

Dear Naval Bhatt,
The business objects:
'BUS1055' - Accounts payable ledger
The business object Accounts payable ledger is ledger that is defined for the representation of accounting transactions with creditors.
It records values at company code level.
'BUS3008' - Accounts payable account
The business object Accounts payable document is an accounting document that contains records on value movements in a company code that are relevant to accounts payable accounting.
Reward points if this is helpful. Close the thread if your query is resolved.
Regards,
Naveen.

Business object for AP invoice

hi all,
 Which business Object is triggered when we AP invoice is created
transaction FB60
thanks in advance
Naval Bhatt

Dear Naval Bhatt,
The business objects:
'BUS1055' - Accounts payable ledger
The business object Accounts payable ledger is ledger that is defined for the representation of accounting transactions with creditors.
It records values at company code level.
'BUS3008' - Accounts payable account
The business object Accounts payable document is an accounting document that contains records on value movements in a company code that are relevant to accounts payable accounting.
Reward points if this is helpful. Close the thread if your query is resolved.
Regards,
Naveen.

Object type for Vendor Invoice (FB60) to attach image

Hi,
I was wondering if any of you experts would know the Object Type for Vendor Invoice which allows an image to be attached to it in early archiving.
Many thanks
G

The object for attaching an image to a document entered directly into FI is BKPF. This is the object for vendor invoices entered into FB60 as well as vendor credit memos (FB65), customer invoices (FB70), customer credit memos (FB75) and GL adjustments (FB50). It also applies to any document posted via a complex (non-enjoy) FI transaction like FB01.

Changedocument for sales invoice creation

When the sales invoice is changed in VF02, an entry is created in changedocument table CDHDR. But when the invoice is created in VF01 no entry is created in the table CDHDR.
Is there a way to enable creation of entry when invoice is created?
The change document object for sales invoice is FAKTBELEG

Hi!
You can try to setup output control for billing document:
- define your own access sequence or expand existing one with one more access based on KOMKBV3-TRTYP field (transaction type)
- assign access sequence to corresponding output type
- maintain condition records for corresponding output type with transaction type "V" - Change
- setup processing routines for corresponding output type. Here it is medium "T" - Tasks (SAP Business Workflow). I didn't try myself to invoke workflow in such a way but it seems this stays for such purposes. Even if not you can try medium "8" - Special function and link your custom program which triggers workflow execution.
This settings will lead to triggering output control whenever billing document is changed or created (this works for standard print medium for me) and invoke workflow execution (almost sure).
Regards,
Maxim.

Business object type for parked invoices

Hi,
We are using documentum to store documents that have been attached to business object types in SAP. The business object types are configured in transaction OAC3 to point to a pre-configured content repository.
Having this configuration allows the object type to use the "services for objects" option, enabling it to store attachments.
The business object types for invoices have been configured and we are able to store attachments. However this does not seem to work for "Parked invoices". The configuration in the "services for objects" component is not there and the feature to store the attachment is disabled.
As the configuration needs to be done for all object types that need to be able to store attachments, maybe someone here can indicate what the object type is for parked invoices. Alternatively, maybe there is a way to look up the various business object types.
Any help you can provide is appreciated.
Thanks.
Kind Regards,
Giwan

Hi ,
Thank You for your reply.
I created inquiry . it takes BUS2031.But BUS2031 is used for quotation.But that inquiry is open in VA12(Change Inquiry) Transaction,not open in VA22(Change Quotation).
Is there any setting for BOR object types to Document Types.
Please give me a reply as early as possible.It's very urgent.
Thanks,
Saritha

Objects related to SD for excise invoice number range

Dear gurus,
Kindly provide the objects related to excise invoice number range for SD module to be updated for new financial year.
[ for ex. j_1excloc ]
Regards
R.Rajendran

provide the objects related to excise invoice number range for SD
Following objects should be maintained in SNUM
J_1IARE1:::::::ARE1 Doc No object based on Series Group
J_1IARE3:::::::ARE3 Doc No object based on Series Group
J_1IDEPINV:::::Excise Invoice Number for Depot Invoices
J_1IEXCEXP:::::Export excise invoice number range
J_1IEXCINV:::::Excise invoice number
J_1IEXCLOC:::::Local excise invoice numebr range
J_1IEXINEX:::::Excise invoice number for export
J_1IINTPR2:::::Despatch serial number
thanks
G. Lakshmipathi

EMIGALL performance for migration object OBJCLASS

Hi all,
my previous question, was Classification of IFLOT & EQUI via CLB2 / CLB1 & was focused on improving performance of classification of IFLOT & EQUI objects.
Testing EMIGALL for migration object OBJCLASS I am seeing no performance gains between a single thread update & parallel update threads. IE the single thread throughput is reported as ~the same as the parallel threads throughput combined.
I note in the job logs of my various tests;
for a single thread, that no messages are logged between the start & end of the migration.
for parallel threads, that message C4 200 'Class "CLASSNAMEHERE" is locked' appearing many times.
I don't see any unexpected migration errors in ether case.
Are there any insights on how I might improve over all throughput using this method? I cant see any control parameters for this object, nor does the Guideline have much information on OBJCLASS.
First world problems :-/

Hello Daniel,
Without having much insight into your system and infrastructure details or the volume that you are working with, I suggest for you to try below for performance improvement.
1. Run DB Statistics on functional location and Equipment related tables such as EQUI, IFLOT, ILOA, etc. (these are HLO objects that you are updating by way of classification). Also update classification table such as AUSP. These tables mentioned here as a starting point.
2. Also strongly suggest that a performance trace be done on this job to analyze and identify another table or steps that may be a performance bottleneck and maybe a candidate for DB statistics refresh Or some other corrective action.
3. The locks maybe occurring due to a mass update which is as expected. Perhaps to get by that you may want to use "commit buffering allowed" option for this migration object and set to say a number "10" or "20" to start with and see if it helps better the performance. As you would have noticed, locks will also impact performance.
4. Please also refer to Cookbook for ISUMIG Performance and refer to sections for DEVICE, CONNOBJ and DEVLOC. These are HLO objects for classification and there may be some useful insight in that document too.
Hope this helps.
Ash

Standard Objects for Goods Receipt and Invoice

Hi experts,
Is there any Standard Object for Creating Goods Reciept and Invoice in SAP other than standard BAPIs

Try to use the PROCESSKEY standard infoobject (BWVORG in R3/ECC) to discriminate the good receipt from the invoice one...
An other option is create a custom generic data source with a view on EKBE table and use the EKBE-VGABE field to discrimate them.
Regards.

Migration / Emulation for 3.x Objects

Hi ,
Though I have BI 2004s currently I have installed BW3.5 Objects (FIAP ODS, CUBE and InfoSources) with In Data Flow Before option.Later I will go for either Emulation or Migration option to convert them into 2004S objects.
Are there any certain steps to be followed to install BI 3.5 Content objects in BI 2004S system? pls guide me.
I have taken the objects given below:
Datasource: 0FI_AP_4 ( Not yet connected to 2004S system)
ODS: 0FIAP_O03
CUBE: 0FIAP_C03
The bottom line is I want to work on the 3.x objects later it needs to be converted into 2004s objects. If someone gives me the step by step approach I really appreciate your help by rewarding the points

1)Replicate datasource as 3.x NOT new
Above DS acts as Emulated
2)Follow same steps as in 3.x ,install business content...load objects
For Migration follow below link
Transformation Rules
Hope it Helps
Chetan
@CP..

Business Object for FB60 Vendor Invoice?

Hi all,
Which is the business object for tcode FB60?
Regards,
Arpita

Hi Arpita,
You should use SWO2 - BO explorer.
Regards,
Suwandi

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

Accounting Document not posted for Cancelled Invoice -error in FI interface

Hi,
When I create a billing document then an accounting document gets created automatically in the background and then when I cancel the billing document no accounting document gets generated and the field Posting Status in header Detail of Billing document updated as "Errors in Financials Interface.
I tried to release it for Posting via VFX3 but failed due to below error message in Log:
"Incorrect doc.no.: 4900000005. Select document number between 3000000000 and 3099999999"
I have checked the Number range assignments to the Invoice type and Accounting type.
The number range is same for both Invoice type (Y0F2) and Cancelled Invoice type (Y0S1).
The Accounting document type (RV) is also same for both the cases. But it is working fine for Y0F2 (Acounting document generated and cleared automatically). But not working fine for Cancelled Invoice (Y0S1).
Can anybody please help me find out a solution to the issue.
Thanks, Ram.

Hi,
The error message F5151 refers to the number range of the FI document.
Please have a look at the note 1259505: FAQ: New cancellation procedure in SD, which covers this issue in detail.
Question 5:
Q5. What is the FI document type, generated by the cancellation ?
In the old cancellation procedure, the FI document type is always
determined in SD, and passed to FI (the same when a normal invoice -
not a cancellation - is transferred to accounting).
In transaction VOFA there is the field 'Document type' (TVFK-BLART).
If this field is filled, then the FI document will have the document
type maintained here.
If TVFK-BLART is empty, then the FI document will get the default
document type 'RV'.
If the new cancellation procedure is performed, the FI document type is
always determined in FI, based on the document type of the FI document
to be reversed.
In transaction OBA7 the FI document type has assigned the field 'Reverse
document type' (T003-STBLA).
If it is filled, then the FI cancellation document will get the document
type maintained here.
If T003-STBLA is empty, then the FI document cancellation will get the
same document type as the cancelled FI document.
Notice that an unexpected FI document type can cause the error message
F5 151.
Example:
F2 invoice 90000001 was released, creating an accounting document with
document type 'RV'.
This F2 invoice is reversed by the S1 billing document 70000001.
In customizing of SD there is:
Billing Type    Document Type
F2              RV
S1
In customizing of FI there is:
Document Type    Number range   Reverse Document Type
RV               00             AB
AB               01             AB
The FI number ranges (object RF_BELEG) are:
No From number    To number   Ext
00 0090000000     0099999999 X
01 0100000000     0199999999
Different situations can occur, due to these customizing settings of the
FI document type, caused by the type of cancellation.
If the new cancellation is used:
The FI document type 'RV' has 'Reverse Document Type' = 'AB'.
Document type 'AB' has number range '01' set as internal.
So the FI document will have its own number included in
100000000-199999999.
There is no issue.
If the old cancellation is used:
The cancellation billing type S1 has no 'Document type' maintained, so
the FI document will get document type 'RV'. It has number range '00',
set as external number range.
So the FI document should get the same number of S1 billing document.
But the S1 billing document has number 70000001, not included in the
interval of number range '01'.
This will cause error F5 151.
I hope this information helps you.

Early Archivelink for vendor invoices

Dear All,
I want to use Early Archivelink for vendor invoices scenario.
I am attaching the scanned document through OAWD by Storing by subsequent entry and i am able to see the work flow item in my in box but i am not able to execute the transaction from here(MIR7).I am using business object BUS2081,method create and task TS30001128.
Please advice how to execute the work flow item from my in box and create the invoice document.
Regards,
Muzamil

Hi,
After maintaining the TS 30001128 as a general task i am able to execute the transaction from my inbox.
Regards,
Muzamil

Migration object for Aggregated Invoice

Similar Messages

Maybe you are looking for