Doc Splitting - Intercompany Vendor Invoice

I am stuck with an issue while posting an inter-company vendor invoice involving two expense line items. 
I have created two debit line items as follows:
40   40000601    service expenses    1000.00      1200 (co.code)
40    4000601     service expenses    1000.00       1400 (co.code)
31       7009        Vendor Colt              2000.00       1200(co.code)
However, while simulating the items for posting, vendor item is not split and each company codes and posting is not permitted saying that no unique company code assignment is found in Company.
Anybody please help me out by telling the splitting rule for this inter-company vendor invoice posting which will help to split the item and posting could be done.

Hi,
  vendor line item is displayed only in the paying company code document information and in the other company code it will be clearing with the paying company code.
For eg:
    Buildings a/c (for company code 1000)  Dr  1500
    Buildings a/c (for company code 2000) Dr  1500
          To Vendor a/c 3000
This is my actual entry.
If my paying company is 1000 then the vendor invoice will be posted completely to the company 1000.
and in the company code 2000 a clearing with company 1000 a/c for Rs 1500 will be generated according to our configuration settings.
System Entries will be:
in company code 1000
Buildings a/c    Dr  1500
Clearing a/c with 2000 Dr 1500
   to Vendor a/c    3000
in company code 2000
Buildings a/c    Dr  1500
  to Clearing a/c with 1000  1500
So there is no Question of Vendor splitting as the invoice is paid by single company.
I think below information will be useful for you.
The way SAP FICO works is that it posts a accounting document in each company code rather than one single posting document. This is beacuse in SAP FICO, one accounting document is always assigned to one company code. A question naturally comes to mind as to how do the debits and credits match i.e. how do accounts balance. To balance accounts, SAP FICO automatically generates line item entries which are posted to a clearing account. Such clearing accounts are normally payables or receivable accounts within company codes. SAP FICO tags cross company code transactions with a common cross company code transaction number for reference. Some examples of cross company code transactions are:
1. Goods are sold by one company code to the another company code.
2. Goods are purchased by one company code from the other company code.
3. One company code makes a payment on behalf of another company code.

Similar Messages

  • Posting Intercompany Vendor invoice

    Hi All,
    While posting the intercompany vendor invoice via VF01 the Idoc generated by RD04 output is errored out with the below error:
    Field BSEG-MWSKZ . does not exist in the screen SAPMF05A 0302
    Please advice......
    Rgds
    Prasad

    Hello Prasad,
    Please check if this helps.
    Please check the master record of the reconciliation account
    with transaction FS03.  Set the field tax category 'SKB1-MWSKZ' to *.
    Regards,
    Raghavendra

  • Automatic Payment Program Proposal split same vendor invoices

    Hello,
    We are facing some peculiar issue in Automatic Payment Program,when we run the automatic payment program payment proposal split the same vendor invoices into so many differnt proposals instead of consolidated proposal.
    Every time it's not happen to same vendor it's dynamically changing to different vendors.
    Eg:We have 10 vendor invoices and when we run the payment run 2 invoices is coming together and 3 invoices coming together not 10 same.
    I have checked the vendor master data and payment program configuration for payment method for company code there is no tick selected for individual payment.
    Could you some body explain me why system is behaving this way.
    Thanks in advance.
    Regards,
    Satya

    Hello Staya
    Just check the line items of your vendor. Some line items may have the payment methods and some line items may not have the payment method. When you do the run in f110 it culbs all the invoices which have the same payment methods together and make the payments. Pls check this and see.
    It could be the reason if you have not ticked the individual payments in vendor master.
    Niranjala

  • EDI Error in intercompany vendor invoice for Argentina

    Hello.
    While issuing and RD04 message for an inter-company customer in Argentina I received error 8A551: Format of reference document number is invalid., as in the attached file; the RD04 message is sent OK but the iDoc fails in 51 status.
    What is the segment/field where reference number is expected? In analysis mode in we05 the segment indicated, E1EDS01 010 Segment 000088 has no field to enter any reference...
    One FI consultant mentioned that this check-up is due to FI document determined during iDoc processing: RE checks the reference number format and we should change it, is there a way to do that through configuration?
    I would like to keep this process as much "automated" as possible, for instance it would be better to have the vendor invoice created but parked pending the proper reference number.
    All inputs are welcome, thank you in advance.

    Thank you Patra, your suggestion can be implemented and I'm pursuing this path.
    This may take up to 1 week to become available in the productive environment so meanwhile I'm also looking to an alternate way to "fix" that. One feasible method suggested by an FI consultant is to change the FI invoice type determined by the system, form RE to a different one.
    Any idea of how can I do that?
    Thank you.

  • How to split the AP invoice into two invoices

    Dear All..,
    Can you tell how can i split the AP vendor invoice which i was posted erlier..i want spil the invoice into two invoices to pay the partial payment to some amount..
    For ex : i have poste one invoice with 50000/- rs..and now i want to split this doc into two like 30000 and 20000, and i want to made the payment for through APP for 30000..
    Can you tell me the step how to do this..
    Advanced thanks
    Bhargav

    If you reverse the original vendor invoice ( credit memo), you can create a new vendor invoice by splitting the amounts with different payment methods. This way APP will pick up only required amount.
    Amount split in vendor invoice can be done by activating "Enable amount split" in OBY6 configuration. This will give you an additional tab "Amount split" in vendor invoice.
    Hope this helps
    Thanks,
    Kalyan

  • Profit center splitting - Intercompany FB60 - Sales/Use Tax Vendor invoices

    We are implementing Use Tax calculations for Vendor invoices and are stuck on an issue with profit center splitting when entering intercompany AP transactions (FB60).     The tax postings of the non-leading company are being split between the two company profit centers.
    When posting a vendor invoice with more than one company the tax items of the leading company are posting with the correct profit center but tax items if the non-leading company are splitting between the profit centers of the two companies.   The total amount of the tax is still correct, just part of it is posted to the wrong profit center. 
    We are assuming this is a document splitting issue but changes to document splitting configuration did not get the desired effect of not splitting the tax accounts.   
    Are there any suggestions of particular areas of document splitting that we should look into or other areas that might be causing this profit center splitting for the tax items?  Any ideas would be appreciated.
    Thanks,
    Jeff

    Hi Murlidhar,
    Here's a sample transaction with the problem results we are seeing.  Normal AP transactions are posting fine, it is only when Sales/use tax is added that we are finding a problem with the profit center splitting.
    Entering a two line FB60 transaction under company 0001.
    Line 1  - Company 0001, profit center 220020, $100
    Line 2 - Company  0002, profit center 250020, $100
    SAP sends this transaction to our external tax system which returns the tax amounts to accrue for each line item.
    Line 1 $7.30 for company 0001
    Line 2 $9.05 for company 0002
    When the transaction is then viewed in General Ledger View we see the tax amount of $7.30 posting to profit center 220020 but the tax amount for line 2 of $9.05 is evenly divided between profit centers 220020 and 250020. 
    The $9.05 should be posting only to profit center 250020 as the profit center assigned to line 2 of the transaction.
    Thanks,
    Jeff

  • FV60 Vendor Invoice Amount Split Tab Field

    Greetings! Our users do not have authorization to access to FB60 - how can we open the fields (OTA and NAME OF OTA PAYEE) in the Amount Split Tab using FV60 - Park Vendor Invoice? Thank you in advance

    Hi:
            In the amount split tab of FV60 there will be a Yellow and blue button on the right corner named as configuration. Just click on it and go to Administrator and there you will see OTA and name of OTA payee . Please see if this has been set as invisible there. If they have not been set as invisible and still you can not see them in FV60 Amount split then the only way to fetch these fields in FV60 is through SHD0...For that please proceed as under
    Go to SHD0...Enter FV60  in Transaction code and ZFV60 in transaction variant.Press create button on the left top corner and enter co code and press enter again when next screen appears, it will take you to the main screen of FV60.. Enter vendor , invoice date,amount , GL account and and its amount and then keep on press entering and giving name to screen where it is required unless a FV60 main screen appears again...Now go to amount split tab and keep on pressing enter unless amount split tab screen appears, data already entered in main screen will be seen by you there , press enter two times times you will see a screen 0090 carrying these OTA fields there you will have to just un check the invisible tick from them and then exit and save with a proper name for screen variant. Give ABAP package name and exit. Upon exit in SDH0 standard variant tab assign and activate this ZFV60 variant and now you will be able to see them.
    Hope it resolves your issue.
    Regards

  • Document splitting: vendor invoice with VAT cannot be posted because of tax

    Hello
    I try to post a vendor invoice with document splitting active. I can post a document without VAT but with VAT (input tax 21%) I get the message "Posting possible only with zero balance" balance; balance on other line items is 210 EUR.
    001 31       0000105675 Vendo                      1.000,00-                V4
    002 40       0000601000 Purchase of consuma           500,00                 V4
    003 40       0000601000 Purchase of consuma           500,00                 V4
    In customizing for document splliting I have following categories assigned to the GL accounts:
    100     399999     01000     Balance Sheet Account
    411000     411000     05100     Taxes on Sales/Purchases
    440000     441000     03000     Vendor
    451000     451000     05100     Taxes on Sales/Purchases
    500000     580000     01000     Balance Sheet Account
    600000     699999     20000     Expense
    700000     759010     30000     Revenue
    The field status group of the tax gl account has following field optional: cost center, profit center, segment (on which document splitting is require)
    What should I do so that the document splitting works also for the tax accounts so that they appear in the gl document?
    kr
    Arjan

    Hi,
    This problem does not seem to be of Document Splitting. When you post the document, balance of the document does not come to zero. This problem somewhat relates to Parrelel currency configured.
    Please depict entire scenario. Let me know in which currency you are posting document and which transaction and what message system is shooting.
    Straight solution can be you manually change the 210 EUR balance into document by clicking on more data.
    Regards,
    Chitnan Joshi.

  • 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                  

  • Error Message Posting a Non-PO Vendor Invoice

    The instance is ECC 6.0.
    While trying to post a non-PO vendor invoice, I am getting the below error message:
    "RKEAK-FIELD(12) is not an input field
    Parked document could not be posted 00 S 347 RKEAK-FIELD"
    Does anyone ever bumped into the same error message or have an idea what is generating the error?
    The issue started happening after one of the accounts in posting (Vendor Discounts) which is a CE was changed to post to Profitability Segment in OKB9. This error was not faced earlier when the account was posting to Cost Centers.
    We are using new GL and Doc Splitting functionality.

    Thanks for your reply.
    I checked the note and it says the affected release are 3.0 D to 3.1G. But we are on ECC 6.0. Moreover, as per the note this is an issue with Tcode FB01, but I am using tcode FB60 for creating the non-PO invoice...
    Please let me know your thoughts...

  • Default profit center when posting vendor invoices thru MIRO, FB60 and FB65

    Hi,
    My requirement is to default profit center at item level while posting vendor invoices using transactions MIRO, FB60 and FB65.
    can anyone please provide some inputs on this.
    Thanks for your help.
    Lucky

    Hi,you need to customize doc splitting.
    1.You need to clasify all accounts from future document in  Document Splitting-Classify G/L Accounts for Document Splitting(e.g. all accounts 2000) 03000-VENDOR.
    2.in IMG: Classify Document Types for Document Splitting    check for Document type  transaction and Variant (e.g. Doc=KR, Trans.=1010, Variant= 0001)
    3.In IMG:  Activate Document Splitting   check  assigned method(e.g. 000012)
    4. in IMG- Document Splitting-Extended Document Splitting-Define Document Splitting Rule
    For find your method and transaction(e.g. Method=00012, trans.=1010) and double click on Item categories(on left of the top of screen)
    There'd be record with category from first step (e.g. Cat.=0300), select one and double click on Base item cat. - there'd be Category 0300 and with check box Automatically split.
    I hope it'd be helpful

  • How is line item split during doc splitting

    Hi Everyone,
    during doc spitting where is the percentage of split  done
    eg: 2 line itmes are split (40 /100.........1st line  itme) & (60 / 100........2nd line itme)
    Regards

    Hi,
    PLease check the Below informaition. We will not specify the Percentage's. Its taken by system as per our postings. for mor information go throw the below information and Examples.
    Information on Document Splitting
        You can use the document splitting procedure to split up line items for
        selected dimensions (such as receivable lines by profit center) or to
        effect a zero balance setting in the document for selected dimensions
        (such as segment). This generates additional clearing lines in the
        document. Using the document splitting procedure is the prerequisite for
        as well as an essential tool for drawing up complete financial
        statements for the selected dimensions at any time.
        You can choose between displaying the document with the generated
        clearing lines either in its original form in the entry view or from the
        perspective of a ledger in the general ledger view.
        For document splitting to be possible, the individual document items and
        the documents must be classified. Each classification corresponds to a
        rule in which it is specified how document splitting is to occur and for
        which line items.
        SAP delivers a set of standard rules that should usually prove
        sufficient. If not, you can define your own set of rules and adapt these
        according to your needs.
        Example
        Example 1: Invoice
        Suppose a vendor invoice containing the following items is entered:
        Posting Key Account     Segment     Amount
        31          Payables                -100
        40          Expense     0001                      40
        40          Expense     0002          60
        Document splitting then creates the following Ledger view:
        Posting Key Account     Segment     Amount
        31          Payables    0001          -40
        31          Payables    0002          -60
        40          Expense     0001          40
        40          Expense     0002          60
        Example 2: Payment
       The payment for the above vendor invoice then contains the following
       items when entered:
       Posting Key Account     Segment     Amount
       50          Bank                    -95
       25          Payables                100
       50          Cash Discount Received  -5
       Document splitting then creates the following document in the General
       Ledger view:
       Posting Key Account     Segment     Amount
       50          Bank        0001          -38
       50          Bank        0002          -57
       25          Payables    0001          40
       25          Payables    0002          60
       50          Cash Discount Received  0001        -2
       50          Cash Discount Received  0002        -3     
    Thanks
    Goutam

  • Doc splitting and new Gl a/c

    Hi All,
    can any one tell me the difference between doc splitting and new gl concept. and explain me how will it useful in preparing profit center wise balance sheet.
    and pls explain me the configuration steps.
    Thanks In advance
    Sarayu

    Hi
    Document splitting enables a complex display of documents. Line items are split here for selected dimensions. This ensures that you can draw up complete financial statements for the selected dimensions at any time. Below example would further clear :-
    Suppose a vendor invoice containing the following items is entered:
    Posting Key Account Segment Amount
    31 Payable 100.00-
    40 Expense 0001 40.00
    40 Expense 0002 60.00
    Document splitting then creates the following document in the general ledger view:
    Posting Key Account Segment Amount
    31 Payable 0001 40.00-
    31 Payable 0002 60.00-
    40 Expense 0001 40.00
    40 Expense 0002 60.00
    Settings for Splitting are as follows :-
    In the IMG, choose Financial Accounting (New)->General Ledger Accounting (New)-> Business Transactions-> Document Splitting.
    1. Classify G/L Accounts for Document Splitting - You need to classify the individual document items so that the system knows how to handle them. You do this by assigning them to an item category. The item category is determined by the account number. In this IMG activity, you need to assign the appropriate accounts.
    2. Classify Document Types for Document Splitting - Every business transaction that is entered is analyzed during the document splitting process. In this process, the system determines which splitting rule is applied to the document. To enable the system to determine the splitting rule, you need to assign a business transaction variant to each document type.
    3. Define Zero-Balance Clearing Account - Here you define a clearing account for account assignment objects for which you want to have a zero balance setting when the balance is not zero.
    4. Define Document Splitting Characteristics for General Ledger Accounting - Here you specify to which document splitting characteristics document splitting applies, for example, profit center or segment. The characteristics that you specify should be maintained in at least one of your ledgers. You determine which characteristics are maintained in your ledger by assigning scenarios or customer fields to your ledgers.
    You also define how this characteristic is to be handled by specifying, for example, whether you want to apply a zero balance setting, whether the field is a required entry field, and the appropriate partner field.
    5. Define Document Splitting Characteristics for Controlling - Here you specify which additional characteristics you want to apply in document splitting. The additional characteristics are not relevant for General Ledger Accounting. Instead, they are relevant for components in Controlling that use documents transferred from General Ledger Accounting.
    6. Define Post-Capitalization of Cash Discount to Assets - Here you define whether the cash discount that is applied in the payment of an asset-relevant invoice should be capitalized to the asset. When you select this setting, the cash discount amount is not posted to the cash discount account in the payment document, but instead directly to the asset.
    7. Edit Constants for Nonassigned Processes - Here you define default account assignments (for example, a default segment) for specific line items in processes for which it is not possible to derive the correct account assignments at the time when the document is posted. This is the case if the required information is not yet available when the posting occurs.
    8. Activate Document Splitting - In this IMG activity, you activate document splitting. The splitting method used is that delivered by SAP as standard, which contains the splitting rules for the different business transactions. If this splitting method does not meet your requirements, you can first define and then select your own method in Customizing for document splitting (see the next step).
    Settings for Extended Document Splitting
    Here you define your own rules for document splitting and make the necessary settings so that the system applies the rules you defined and not the SAP standard rules.
    9. Define Splitting Method - Here you define your own method for document splitting. A splitting method contains the rules governing how the individual item categories are dealt with.
    10. Define Splitting Rule - Here you define the splitting rules for document splitting. You assign one or more business transaction variants, the account key for the zero balance setting, and the leading item categories for cross-company code transactions to a splitting method.
    11. Assign Splitting Method - Here you assign the splitting method to be used for document splitting after activation. If you want to activate your own splitting method, replace the standard method with your own method.
    12. Define Business Transaction Variants - Here you can define business transaction variants for the business transactions in document splitting.
    Regards,
    R.Ramakrishnaraj

  • Billing doc splitting to different cocodes

    hi gurus,
    my client needs billing doc splitting to different cocodes  with different revenue G/L accounts  with common customer.  He needs from billing doc flow ?how can we solve this? any inputs on invoice splitting highly appreciated.
    thanks in advance.
    regds,
    ram

    Hi,
    I am facing a similar issue. Please let me know a s how you proceeded in clearing the "SPLIT DUE TO PARTNER DATA".
    Thanks in Advance.
    Regards,
    Rajesh

  • Error 'No tax code found for difference' in Posting Vendor Invoice IDOC

    Hi All,
    I am getting error message 'No tax code found for difference' while posting Vendor Invoice IDOC into SAP. IDOC type is INVOIC02. There is no difference in PO price, Invoice price and even Standard price. then why this  error message? Other Vendor EDI settings are done ( OBCA, OBCD, OBCE etc). Is there any thing specific to be done in the config for this error?
    IDOC has PO  as reference document.
    I looked into several threads in SDN forum but could not find proper solution
    Can any ine help me with this issue?
    Thanks in advance
    Hari

    Hi
    You might be  missing the tax code for uploding through IDOC
    so you can use the t.code we02 and give the doc and find the error
    go to the WE19 to edit the tax  code
    and USE the t.code  BD87  to select the doc and process it
    thanks
    Madhu

Maybe you are looking for

  • Cant find message center number on BlackBerry 9530

    i need help ..... im getting frustrated by the minute. my screen cracked and i sent my device to be fixed, i got it back and i can't seem to send text messages (but i can receive them). I'm told that i need to change my service center number (and i h

  • Help required: class assignment and values for functional location

    Hi All, My requirement is to get classification data for a functional location as in IL03. Can any one let me know where in the standard program are they getting the assigned classes and class values. So that I can use the same logic. Thanks.

  • Problem with select query

    Hi All, i_dfkkko-xblnr   IF NOT i_dfkkko[] IS INITIAL       .     SELECT opbel            belnr            FROM erchc            INTO TABLE i_erchc1            FOR ALL ENTRIES IN i_dfkkko            WHERE opbel EQ i_dfkkko-xblnr.   ENDIF. I am using

  • How to pass a user defined table type to stored procedure?

    Hi, I am trying to call a stored procedure from Java. The store procedure has three IN parameter, 2 IN/OUT params and 3 OUT parameters. The two IN/OUT parameters are user defined objects. Can anyone tell me how to set these IN/OUT parameters in Java.

  • Safari freezing on certain sites

    Hi Frustratingly Safari is freezing on certain sites and I'm forced to do a Force Quit. I think these sites may have a Flash player but not sure. Any remedies??