Payment of commission.

Hello
Dear sir can you give me a detailed idea about the Payment of commission?
Thanks in advance.
Regards
Dileep Singh

Hi,
I want to know  about the commission payment for our customer after automatically calculation.
i m just working in a textiles division.
Thanks allot for responding.
Thanks  & Regards
DSRajput

Similar Messages

  • Commission Agent

    Hi,
    I have searched for commission agent config. in forum but didn't find satisfactory answer.
    I have to map Commission agent scenario in sap,
    Commission Agent  places sales order to company but ship to party is different. Commission is given to agent on sales value in every 3 month.
    How can payment of commission is made in every 3 month in sap.
    Kindly guide me on above scenario.
    Thanks & Regards,
    Hemu

    Hi,
    As per your post I understand ship to party is different but Who is your sold to party and who is commission agent
    Are sold to and commission agent are same ???? or different ????
    Manage it with rebate process or else with commission agent enhancement which is in below link
    http://www.sap-img.com/sap-sd/steps-to-create-commission-for-agent.htm
    Kapil

  • Commissioning Agent Issue .

    HI
    The commission agent name and percentage of commission is required at the sales order and after the completion of the sales of the sales activity i.e receipt of payment the commission agent is paid on the basis of percentage of cleared payments.
    In order to do so i made the following configuration:
    The Partner function(ZC) is created ,by copying the SP, in setup Partner Determination for Sales Document Header.
    The account group 6000 is assigned to the Partner function(ZC) in Accounts-Groups Function Assignment.
    A new entry has been made in Partner functions in Procedure by considering (TA) as partner Determination Procedure and ZC as the partner functions.
    A new entry has also been made in Partner determination procedure assignment by considering STOR as the sales doc type and TA as the partner determination procedure.
    The account group for commission agents:
    A new account group(ZCOM), has been defined in {Define Account groups with screen layout(Customers)}.
    The number ranges creation for customer Accounts and its assignment has been done.
    Considering Commission agent as the seperatre master data therefore:
    A new Partner function(ZC) is also created with the partner type as KU in the Setup partner determination for customer master.
    A newAccount group-function assignment is created with partner function ZC and account group ZCOM.
    A new entry ZC is created in the Partner determination procedure.
    A new entry has also been created in the Partner Functions in procedure with Partner determination procedure ZC and partner function as ZC.
    A new entry has also been maintained in the Partner determination Procedure Assignment with Group as ZCOM and partner determination Procedure as the ZC.
    Result;
    During the creation of the customer in XD01,ZC as a partner function is not appearing there.And when i enter ZC as my partner function,system gives me following error.
    In table TPAER, the entry AG ZC  is missing.
    Please tell me what mistake i done in the configuration and is there any thing left there?
    Regards:Vijay Kumar

    Dear Damodhar Reddy
    In the t-code VOPA for the customer master, in partner determination procedure ZC ,I have maintained the partner functions as partner function=ZC and the partner type=LI.
    The Account Group ZCOM is assigned to the Partner determination ProcedureZC.
    But still when i make the new customer with t-code xd01,i don't find the Partner functionZC their in the grid or when i enter the partner functionZC,the system gives the error which is as follows:
    In table TPAER, the entry AG ZC  is missing.
    Please tell me how can i rid of this error.
    Regards:Vijay

  • Error while doing IV for Service Delivery Payment

    Dear Support,
      There is Problem while doing Invoice for delivery Payment(Agent commission) in case of Service Order having without
    account assingment.
    While doing Invoice for that Delivery cost , system is giving a error message 'Enter a GL Account'.
    Pls provide some solution regards .
    Ragerds
    Mukesh

    Hi,
    if your service order is a service purchase order, please read the following:
    Planned delivery costs are not supported for service orders.                    
    There is no plan to change this in the near future.  
    Delivery costs are generally not supported in external services                
    management and in case of blanket purchase orders, item category D or B.       
    Instead of representing delivery costs via conditions, in case of              
    service documents, freight costs and other, SAP recommends to add in           
    additional service lines. (note 381030 )                                                                               
    For the future we recommend to use additional service line instead              
    of planned delivery costs condition. There is no problem to post                
    invoice for different vendor for particular SES created for service             
    line that constitutes delivery costs.    
    Regards,
    Edit

  • Salesperson commission

    2 qs reg salespersons:
    a)Where do I mention the commission amount received by a salesperson against an order ?
    b)How is the payment of commission handled in financials? I mean, the commssion paid should be a paybles invoice; how is this taken care of?
    thanks

    Yes you need a separate module for this. There is no native capability in OM or AR for calculating or paying commissions. If your commission plan is simple enough, e.g. no quotas, straight percentage based commission, no clawbacks, no disputes, etc., then you could probably get away with some simple custom solution. Otherwise, you need to look at OIC.

  • How to add Characteristic text to Key figures in Bex report?

    The result set of a report is like this
                                          Q1             Q2            Q3           Q4
    Payment amount      Payment          2000           4000          1200         1400
                        Recovery         1200           1400           100          200
    Commission          Payment          4000           5000          2000         2000
                        Recovery         2000           2000           100          100
    Total               Payment          1500           1200          5000         4000
                        Recovery          600            200          1000          200
    The first Column Payment amount, Commission and Total are key figures.
    Payment  and recovery are text of a Characteristic Infoobject ( Flag type : X = Payment, # = Recovery ).
    Now the requirement is not to have Characteristic Infobject as Column but to have them as text beside keyfigure.
    LIike this
                                          Q1             Q2            Q3           Q4
    Payment amount (Payment)             2000           4000          1200         1400
    Payment amount (Recovery)            1200           1400           100          200
    Commission (Payment)                 4000           5000          2000         2000
    Commission (Recovery)                2000           2000           100          100
    Total (Payment)                      1500           1200          5000         4000
    Total (Recovery)                      600            200          1000          200
    How to achieve this kind of result?

    Create Restricted Keyfigures to achieve this requirement.
    create 2 RKF for Payment Amount Keyfigure
    Create RKF1 with Payment Amount keyfigure and restrict flag type with "X" and then
    Create RKF2 with Payment Amount keyfigure and restrict flag type with "#".
    And use the RKF's in the query.
    Similarly create two RKF's for each Keyfigure used in the query and restrict it with flag type.
    --- Thanks...

  • Linking Deliveries to a particular Driver

    Hi.
    1) I created a 'Route Sales' order (No. 25) and completed the order by generating:
           a) Delivery Number (No.100),
           b) Shipment Number (No. 2001).
           This transaction can be linked back to the driver for payment of commission through tables VTTK,VTTP,LIPS etc.
    2)Along the route, Sales Orders (No. 26) and Delivery (No. 101) and several others were created for customers but these deliveries cannot be linked to any shipment.
    Logically, Delivery No 101 belongs to Shippment No 2001(in my example), but this is not the case. NO SHIPMENT DETAILS EXIT for the subsequent sales and deliveries.
    HOW can I link delivery no 101 to a shipment and to the driver.

    The issue was resolved by other means.

  • Two billing for one sales order for same customer

    Dear All ,
    I have a requirement of posting a two billings for one sales order.
    One is for Sales and another is for commission...
    Entry could be
    Sales Entry - Db Customer
                        Cr  Sales
    Commission entry could be
    Db - Cusomter
    Cr- Sales commission income account (P/L)
    We are having third party sales scenario , In this case billing is MIRO dependent.
    Once the miro is done then only billing is possible ...
    Could you please advise on that ..
    Regards,
    Sukh

    Dear Ratish,
    Thanks for yr reply.
    I already did that but it is not serving business purpose.
    Comm payment  - comes diff time than sales payment.
    so ,I will post one entry customer will get hit with total amount Sales + commission
    like below
    Let say 10, 000 is the sales value and 500 is the commission
    So , This entry will get posted
    Customer Db- 10,500
    Sales Cr- 10,000
    Comm Income Cr- 500
    But, As I said sales amt will be paid before so We need to clear it partially and some time customer pays also diff amount due to some defect.
    So, We wont be knowing for which case we have or havnet received the payment against commission.
    As , Customer account is got hit with total amount( Sales+ Comm..value).
    Pls advise how to solve this.
    Regards,
    Sukh

  • Invoice request based on multiple sales order for same customer

    Hi Team,
    I just wanted to know if we can create manual invoice request based on multiple sales order for same customer?
    For project based invoice request i have create based on single invoice request.
    Appreciate your input here.
    Thanks,
    Nitin

    Dear Ratish,
    Thanks for yr reply.
    I already did that but it is not serving business purpose.
    Comm payment  - comes diff time than sales payment.
    so ,I will post one entry customer will get hit with total amount Sales + commission
    like below
    Let say 10, 000 is the sales value and 500 is the commission
    So , This entry will get posted
    Customer Db- 10,500
    Sales Cr- 10,000
    Comm Income Cr- 500
    But, As I said sales amt will be paid before so We need to clear it partially and some time customer pays also diff amount due to some defect.
    So, We wont be knowing for which case we have or havnet received the payment against commission.
    As , Customer account is got hit with total amount( Sales+ Comm..value).
    Pls advise how to solve this.
    Regards,
    Sukh

  • Commission Query not picking up payment on Account linked later

    Hi Experts,
    I created a query for a Client who need to pay Sales Commission to Sales Employees. This report must show only the Invoices that was Paid.
    The Query works fine, exept that it will not pick up the following Payments: When they makie a Incoming Payment on Account and then later link it to an Invoice via the Internal Reconciliation screen.
    SELECT T0.[DocNum] AS 'Incoming Payment', T0.[DocDate] AS ' Incoming Payment Date', T0.[CardCode], T0.[CardName],  T3.[SlpName], T3.[Commission], T1.[DocNum] AS 'Invoice Number', T2.[OpenSum] AS 'Invoice Line Amounts', T2.[OpenSum] * T3.[Commission] / 100 AS 'Commission Amount'
    FROM ORCT T0  INNER JOIN OINV T1 ON T0.DocEntry = T1.ReceiptNum INNER JOIN INV1 T2 ON T1.DocEntry = T2.DocEntry INNER JOIN OSLP T3 ON T1.SlpCode = T3.SlpCode
    WHERE T0.[DocDate] >=[%0] AND  T0.[DocDate] <=[%1]
    How can I get these Invoices that was linked to a Payment to also show in this query?
    Thanks,
    Marli

    I know that this is an old post, but in case someone else wants to use this code I wanted to point out that this code assumes that only invoices are included in payments.  If other types such as deposits or credits are included in the payment, then you will get the wrong results.
    Need to change the link to OINV slightly to check the document type for Invoices
    JOIN
    OINV T1 ON T1.DocEntry = T4.DocEntry AND T4.InvType = 13 -- AR Invoice Hdr
    Then need to do this same for the other possible document types.

  • Commission on Credit card Incoming payment

    How to give effect to commission dducted by Credit Card company on Incoming Payment by Credit card.
    thanks in advance

    Please check this thread:
    Re: Management of Invoice financing
    Even though it is not directly answering your question, hope it is useful.
    Thanks,
    Gordon

  • Agent Commission Payment via Rebate settlement or any other

    Hi Gurus,
    In our scenario: My client business is 90% through Agents (i.e both Domestic and Exports).
    Client wants to settle the commission 1. immediately after the invoice 2. monthly 3. quarterly.
    Could you please throw light immediately to address this issue.
    As per SDN -  I have configured FA as a partner function to the Customer. But the rebate agreement will be settled with customer. But how to settle that directly to the Agent.
    Through VA05 list the sales orders per the FA and settle it manually or
    Credit memo request to the amount (%) per each and every sales order.
    Please respond to this ...
    Thanks in Advance
    Cheers
    Srikanth

    Hi Gurus,
    Could anybody explore further with details.
    Regards
    Srikanth

  • Commission  Agent Payment

    Dear All,
    I have a scenario in which client wants to pay commission on sales. In this case commission will be paid on the basis of sale made and amount of commission from return will be deducted.
    For this I give the solution to create new condition type which is static and create new partner function as agent and also create   a new report on the basis of time and agent basis which tells us the net amount payable to vendor.
    At the end of the month user will run the report and get the net amount of commission. End of the month user will create a purchase order and will do MIRO. once the vendor invoice is created the same amount will settled by using APP process.
    Please let me know if there is any gap or is there another way to automatic settle the commission amount. Please let me know if there is another procedure which reduce the user efforts.

    Hello,
    Request you to search the Forum before creating new thread.
    Check the follow WIki & Threads:
    1. http://wiki.sdn.sap.com/wiki/display/Community/CommissiononSales%28AccountingEntryfromSales+Invoice%29
    2. Re: Commission on Sales
    Hope this helps,
    Thanks,
    Jignesh Mehta

  • Posting of Commission Exp to calculate the Cost of Goods Sold

    Hi Team,
    I do work in an automobile manufacturing organization and is new to SAP FI module. I have a business requirement which I need to fulfill; I would appreciate if all you gurus help me with finding the solution.
    Business Scenario:  at present, we are posting the following entries to record the commission we paid to dealers for selling vehicles.
    Commission Exp (DR)
         Customer (CR)
    Customer (DR)
         Dealer (CR)
    With these entries we are not been able to track the commission based on vehicle variants i.e. Toyota GLI, XLI etc.
    New Requirement:
    To calculate the Cost of Goods Sold for a variant, I need to track the commission expense based on vehicleu2019s variants. Please help me in finding the solution.
    Thanks

    Thanks for quick response.
    Let me give little more details of type of commission entries we have
    1) Normal Commission - Fixed commission variant wise and is derived from SD.
    2) Additional Commission - No predefined formula, this is totally based on top management discretion. Management decides how much would be paid to a particular dealer.
    3) Sliding Commission deduction - Deduction of certain amount from commission on late payments.
    4) Additional Sliding Commission - Payment of additional commission based on early payment terms.
    Currently, FI department is calculating all these figures on Excel sheets and then post a JV for each type of above mentioned commission.
    How can I configure the system to calculate these amounts automatically without involving Excel Sheet help?
    and how to post these amounts variant wise along with dealers and customers.

  • 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                  

Maybe you are looking for

  • Enhancement of ds 0FI_AA_12

    hello I need to enhance ds 0FI_AA_12 (depriceation) with some fields from table ANLP. Is there any trucky includewhich allows to do automatically (like for ds 0FI_AA_11)? Alex

  • PSE 4 Mystery on Keywords and File Info

    I use PSE 4 for organizing my photos only. I edit in PS CS and then "get" the edited files from the External HD to organizer and tag them. The tags show up in File Info as keywords. Great. If i go back to PS CS and do File Info the keywords there are

  • Accounting document not made for Intercompany

    Hi Friends, My question is for interoffice customers sometimes need to fill in the Transportation code i.e., in Invoice Header data - "Foriegn Trade/Customs":   Tab - "Handling" Tab:ModeOfTrnsprt-Border - 3 (Road)                                     

  • Network connection very slow, lot of drops

    Hello! On my network, there's an ADSL modem; an AirPort Extreme is connected to it and all my computers are connected to that AirPort Extreme. Initially, I had set the AirPort Extreme as a bridge and the modem was in PPPoE. However, I had weird troub

  • Plan data from 2 applications(mulitprovider)

    Hi Experts, I would like to see plan data of 2 bpc applications( X & Y) via bex query.  our version is bpc75nwsp04. By default when application created in bpc, system generates one mulitiprovider.  In my case, i used mulitprovider of X and in that in