Cubes for Billing, BAcklog and Sales forecast

HI
I want to know the cubes for the following. Billing, BAcklog and Sales forecast
Regards
sam

Hi,
You can use 0SD_C03 cube for billing and all related to sales or using 2lis_13_vditm and 2lis_13_vdhdr youcan create your own ODS for billing.
http://help.sap.com/saphelp_nw70/helpdata/EN/38/0c853c01c89d7ce10000000a11405a/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/71/1769372b2b7d20e10000009b38f842/frameset.htm
Regards.

Similar Messages

  • Account Creation - Badi for Default values for BP Role and Sales Area

    Hi all,
    my requirement regards the possibility to create a new prospect (a link should be available in the navigation bar or create section).
    Logically, a bp role as "Prospect" and particoular sales area should be created automatically.
    I created an implementation for the BADI definition "BADI_CRM_BP_UIU_DEFAULTS". But don't know how to create the default values for BP role and Sales area:
    In my code
    assign cr_me->('VIEW') to <lv_view_name>.
      if sy-subrc ne 0.
        exit.
      endif.
      lv_viewname = <lv_view_name>.
      case lv_viewname.
        when 'AccountDetails.htm'.
    I obtain the viewname "AccountDetails" , the related context "Header". After I don't know how to proceed to obtain the related entities through the relationship BuilRolesRel and BuilSalesArrangementRel.
    Am I following the right way? Is there another solution to prepare the output for default values?
    Any kind of suggestion will be appreciated.
    Regards, Roberto

    go to spro>cross-application components>sap busines partner>business partner> basic settings>field groupings>Configure Field Attributes per BP Role
    Double click the business role which you want to customaze (e.g. 'A') and change the proper settings.
    Regards.

  • Special G/L transactions not defined for bills/exch.and down pmnts ERROR

    Dear Experts,
    I am trying to park document via F-63 - Invoice Parking - General  to park  down payments made to vendor using following details in initial screen for F-63:
    Posting Key_____29
    Account number _1000
    SGL Ind ________A
    after pressing enter key the system prompt error message that is:
    Special G/L transactions not defined for bills/exch.and down pmnts
    Message no. FP030
    Diagnosis
    You have selected a posting key with a special G/L indicator of type 'Bill of exchange', or 'Down payment'. Document parking is not defined for special G/L transactions of the type 'Bill of exchange' or 'Down payment'.
    System Response
    Document parking cannot be carried out.
    Procedure
    Select a different posting key or special G/L indicator. If the posting is a 'One-time posting' to a rent contract, select a different transaction type or post the document directly.
    HOW CAN I PARK DOWN PAYMENT DOCUMENT FOR VENDOR. KINDLY PROVIDE SUITABLE SOLUTION.
    REGARDS

    Dear,
    Your special G/L "A" is set as Down Payment/Down Payment request, this is what cause the error.
    To meet your requirement just go to FBKP select special G/L "A" enter your chart of accounts and go into properties, change
    Special G/L transaction types to Others from Payment/Down payment request.
    Advances can be created as Special G/L transaction types Others
    If parking is utmost required by you then according to me you should create two special G/L for Down Payment. New created should be used for parking and default by SAP you can use with functionality like F-47, F-48, F-54.
    System is stopping you because down payment functionality is provided exhaustively in SAP so you should follow that.
    Please analyze the process exhaustively and implement to smoothen your process.
    Regards,
    Chintan Joshi.

  • Special G/L transactions not defined for bills/exch.and down pmnts

    Dear Sapguru,
      When i am down payment parking through F-65, and giving special gl indictor.
    Error:---Special G/L transactions not defined for bills/exch.and down pmnts
    Message no. FP030
    Diagnosis
    You have selected a posting key with a special G/L indicator of type 'Bill of exchange', or 'Down payment'. Document parking is not defined for special G/L transactions of the type 'Bill of exchange' or 'Down payment'.
    System Response
    Document parking cannot be carried out.
    Procedure
    Select a different posting key or special G/L indicator. If the posting is a 'One-time posting' to a rent contract, select a different transaction type or post the document directly.
    Thanks.
    Dharma.

    Did you define spec. GL through OBXR (customers) or OBYR (vendors)?
    regards

  • VF01 Determine Billing date for billing index and printout to current date

    Hi
    we need to determine the Billing date for billing index and printout to current date
    What can I do to determine automatically at the time of creation current day to Billing date for billing index and printout?
    please let me know
    Best Regards,

    Hi Beatriz ,
    You have two options here. you can chose either of these solutions:
    1.
    A. T-Code: VTFL ( if using del related billing)   For the billing document and delivery, at item level assign the copying requirement 011 or if you are currently using some other routine then you can use following in that
    VBRK-FKDAT = SY-DATUM.
    B. T-code VTFA (if using order related billing)
    Similar to A, using copying requirement 011.
    2. You may also try option of Checking in the User Exit for the Program RV60AFZA & RV60AFZA.
    Please let us know if this helps
    Regards
    Harpreet

  • No company code found for plant 0001 and sales organization 0001

    Hi BW Experts,
    I am using the datasource 0PLANT_ATTR.While loading the data, i am getting the warning message as "No company code found for plant 0001 and sales organization 0001". I have replicated all the Currencies by using the "Global Settings".Do i need to do any settings in BW Side.
    Please help on this Issue.
    Thanks,
    Ram

    Hi Ram,
    It is not pertaining to the Currency translations or any?
    The warning message is because:
    In the 0PLANT there is 0comp_code as attribute; while loading the data from 0PLANT_ATTR datasource there for that particular PLANT "0001" and Sales Org "0001" system couldnt find the 0comp_code.
    As it is not maintained in the R/3 system.
    This is why the warning messages are coming out..
    Hope you understood...
    Regards,
    Ravi Kanth

  • Table for Billing Details(in Sales Area Data) in BP

    Hi,
    Can you let me know the table name for Billing Details(in Sales Area Data) in BP xn.
    Please Help.
    Neeraj

    Hi,
      CRMD_BILLING Contains billing related information.
    see these tables also..
    CRMD_BILLPLAN
    CRMD_BILLPLAN_D
    CRMD_BILLPLAN_DA
    Regards
    Srinu

  • Data Loading issue - No local currency found for plant 0001 and sales org

    Hi Guru's,
    I am trying to load data to 0PLANT_ATTR and I am getting the following error message:
    1. No local currency found for plant 0001 and sales organization 0001
    2. Plant 1010 : No sales organization found; Local currency cannot be checked
    I have also maintained the global setting for currencies in RSA1 for that particular Source System.
    Please let me know how to resolve this issue.
    Thanks in advance.

    Hi,
    Refer the lnik and the note mentioned it.
    Re: Problem when storing master data 0PLANT_ATTR-Full (i.e. Full Update)
    With rgds,
    Anil Kumar Sharma .P

  • Just bought an itunes card but when buying music, its asking for billing info :/ and no taking the money of my reedemed card

    just bought an itunes card but when buying music, its asking for billing info :/ and no taking the money of my reedemed card

    Update your credit card info.
    This is how iTunes verifies your account.

  • Billing table and Sales table relation

    Hello,
    How is the billing table and sales table related to each other. I meant which is the field that keeps relation between two tables?
    Thanks
    Rakesh

    vbrk and vbrp are billing tables.
    vbak and vbap are sales tables.
    likp and lips are delivery tables
    vbkd is sales doc business data.
    vbrp-vgbel = lips-vbeln.
    vbrp-vgpos = lips-posnr.
    lips-vgbel = vbap-vbeln.
    lips-vgpos= vbap-posnr.
    VBKD-VBELN = VBRP-AUBEL
    regards.
    santhosh
    Message was edited by:
            Santhosh Reddy

  • Wht r the standard tables for vendor customer and sales order report/

    Hi wht r the standard tables for vendor and customer reports and is how in normal we cannot use them for vendor reporting and etc ?

    Hi
    Customer is related to Sales Module
    So for a customer we fetch the reports of Sales orders , Deliveries and Billing doc's
    CUstomer and Vendor related tables with important fields:
    KNA1: Customer Master-General(KUNNR,NAME1,LAND1)
    KNB1: Customer Master(Company Code)(KUNNR,BUKRS,PERNR)
    KNC1: Customer Master Data (Transaction Figures)(KUNNR,BUKRS,GJAHR)
    KNVK: Customer Master Contact Partner(PARNR,KUNNR,NAME1)
    KNVV: Customer Master sales data(KUNNR,VKORG,VTWEG,KDGRP)
    KNBK: Customer Bank Details(KUNNR,BANKS,BANKL,BANKN)
    KNVH: Customer Hierarchy (HITYP,KUNNR,VKORG,VTWEG,SPART)
    KNVP: Customer Master Partner Functions(KUNNR,PARVW,KUNN2)
    KNVS: Customer Shipment data(KUNNR,VSTEL,TRANS)
    KNVI: Customer Tax data(KUNNR,ALAND,TATYP)
    LFA1: Vendor Master-General (LIFNR,NAME1,ORT01)
    LFB1: Vendor Master(Company Code)(LIFNR,BUKRS,PERNR)
    LFC1: Vendor Master (Transaction Figures)(LIFNR,BUKRS,GJAHR)
    Sales related Tables for a customer
    VBAK: Sales Document(Header Data) (VBELN, KUNNR)
    VBAP: Sales Document(Item Data) (VBELN,POSNR,MATNR,ARKTX,CHARG)
          Enquiry, Quotation, Sales Order are differentiated based on Doc.
          Type(VBTYP field) in VBAK,VBAP Tables( for Enquiry VBTYP = A,
          for Quotation 'B' & for Order it is 'C'.)
    LIKP: Delivery Table (Header Data)(VBELN,LFART,KUNNR,WADAT,INCO1)
    LIPS: Delivery Table (Item Data)(VBELN,POSNR,WERKS,LGORT,MATNR,VGBEL)
          (LIPS-VGBEL = VBAK-VBELN, LIPS-VGPOS = VBAP-POSNR)
    VTTK: Shipment Table (Header Data)(TKNUM)
    VTTP: Shipment Table (Item Data)( TKNUM,TPNUM,VBELN)
          (VTTP-VBELN = LIKP-VBELN)
    VTFA: Shipping Document Flow(TKNUM,VBELV,VBELN)
    VTPA: Shipping Partners data(VBELN,PARVW,KUNNR,PERNR)
    VTTS: Stages in Shipment(TKNUM,TSNUM,TSTYP)
    VTSP: Transport Stage/Shipment Item Allocation(TKNUM,TSNUM,TPNUM)
    VEKP: Handling Unit: Header(Packing)(VENUM,VSTEL)
    VEPO: Handling Unit: Item (Packing)(VENUM,VEPOS,VBELN)
    VBRK: Billing Table(Header Data)(VBELN,FKART,BELNR)
    VBRP: Billing Table(Item Data)(VBELN,POSNR,FKIMG,NETWR,VGBEL,VGPOS)
          (VBRP-AUBEL = VBAK-VBELN, VBRP-VGBEL = LIKP-VBELN)
          Apart from these tables there are lot of other tables which starts with
          ‘V’, but we use the following tables frequently.
    VBUK: All Sales Documents status & Admn. Data(Header)(VBELN,VBTYP)
          VBTYP= ‘C’(Sales Order) VBTYP=’J’(Delivery) VBTYP=’M’(Invoice) 
    VBUP: Sales Documents status & Admn. Data(Item)(VBELN,POSNR)
    VBEP: Sales Doc. Schedule Lines Data(VBELN,POSNR,EDATU,WMENG)
    VBKD: To get sales related Business data like Payment terms etc.(VBELN,ZTERM)
    VBFA: sales document flow data(VBELV,VBELN,POSNV,VBTYP)
    VBPA: Partner functions Data(VBELN,PARVW,KUNNR,LIFNR)
    VEDA: Contract Data(VBELN,VPOSN)
    VEDAPO: Contract Data(VBELN,VPOSN)
    Vendor related MM tables
    EBAN-- Pur.Reqn. Data (BANFN,BNFPO,BADAT,MATNR)
    EBKN-- Purchase Requisition Account Assignment(BANFN,BNFPO,VBELN)
    EINA—- Purchase Info.Record (General Data)(INFNR,MATNR,LIFNR)
    EINE-- Purchase Info.Record (Pur.Orgn Data )(INFNR,EKORG)
    ELBK-- Vendor Evaluation Header Data(LIFNR,EKORG,KLASS)
    EKKO-- Purchase Order Data (Header)(EBELN,BSTYP,BSART)
    EKPO-- Purchase Order Data (Item)(EBELN,EBELP,MATNR)
           RFQ and PO are differentiated by Doc Type(BSTYP)in EKKO table.
           For RFQ it is ‘A’ and for PO it is ‘F’.
    MKPF-- GRN Data (Header) (EBELN,BLDAT,BUDAT,XBLNR,BKTXT)
    MSEG-- GRN Data (Item)(MBLNR,BWART,LIFNR,MATNR,EBELN)
           Apart from this there are lot of tables which begin with 'M'& 'E', but we
           use the following very often.
    EKBE--PO History Data (EBELN,EBELP,BELNR,BLDAT,MATNR,VGABE)
    EKBZ--PO History with delivery Costs(EBELN,BELNR,LIFNR,XBLNR)
    EKET--Schedule lines data of a PO (EBELN,EINDT,SLFDT)
    EKES--Vendor Confirmations Data(EBELN,EBTYP,EINDT,XBLNR)
    Reward points if useful
    Regards
    Anji

  • Currency Conversion for billing doc and after user exits in COPA

    Hello Friends,
    Need your view on this issue:
    1. Company codes currency and Operating currency is different., Costing Based CO-PA.
    2. Value filed "Gross Sales" get posted via Billing doc. In case of correction billing or re-posting (after reversal of original one) of billing doc value
    field "Gross sales" get posted based on exchange rate of original (very first) posted document because system is updating "Translation date"
    in table BKPF from very first document posted and not taking current date as a translation date. SAP standard program is  reading "Translation date" from BKPF to chose exchange rate and valuating "Gross Sales" on that ex.rate.
    3. Some user exits in COPA valuation to populate some values for other value field (Example - Gross Sales value should populate in value field
    "Sales ASP"). After valuation in exits, SAP standard program is re-valuating value fields value (program statement is : perform currency conversion for fields that were changed in exit ) and for this valuation system is taking posting date for exchange rate.
    Due to above logic company code currency value is different in Gross Sales and Sales ASP.
    Requirement is : Sales ASP value should be same as Gross Sales.
    Can you please share your thought to find the solution.
    Thanks
    Ravi

    Check if the currency key and the unit of measurement are filled in (these will be the reference fields specified in the field definition of the structure at the database level).

  • Table name for tracking delivery and sales order

    Hi,
         What is the table and field name for tracking the delivery and sales order in SD
    Regards

    Hi,
    If you want the DELIVERY DOCUMENT individally you can get it from the LIKP-VBELN
    In the same way the SALES DOCUMENT from VBAK--VBELN
    If want to get the DELIVERY DOCUMENT AND SALES DOCMENT from the VBFA with the Sbsequent document category
    M is the subsequent category for BILLING
    j                                                       DELIVERY
    regards,
    santosh

  • Question - SD user exit for Billing with multiple sales orders

    We have a situation where we are summarizing Accounting Billing document updates via OBCY, transaction type VBRK .
    We will also have multiple sales orders per billing document.
    One of our accounts is a COGS- clearing account which will post for both delivery and billing documents.
    Our goal will be to clear the COGS-clearing account after the delivery and billing has occurred.
    One alternative being evaluated is to update the assignment field ( bseg -zuonr) for the sales order. 
    To do this, one of the SD user exits , perhaps SDVFX008, would be necessary to update the sales order from vbrp-vbel2 to bseg-zuonr.
    I am concerned about
    1) will the update work
    2) what will be the effect on summarization
    If we try to implement the user exit , would we be successful to just update the assignment field for just the COGS accruall account.   _Therefore the next effect is that AR,Rev, etc, would summarize , but the COGS clearing would break out due to the update to the assignment field..
    Does anyone have any experience similar to this situation.
    Thank you,
    Jeff

    Hi
    You can use SDVFX008 or FI Substitution exit RGGBS000 (Form U100)
    You can very well update the required GL (COGS Clearing) with the Sales order No... However, how exactly it would behave upon summarization, I am not sure about that.. you need to develop that and see
    In the COGS account during PGI, Sales Order No is populated always in the field "Sales Order"... In your case, the COGS clearing account should be having sales order no populated...
    So, if you are successful to populate Sales Order No during billing in the "Sale Order" Field for the COGS clearing account, that should also suffice...
    or See if you can have relevant sort key in FS00 for the COGS clearing account so that Sales order no is always populated..
    Regards
    Ajay M

  • How the data is fetched from the cube for reporting - with and without BIA

    hi all,
    I need to understand the below scenario:(as to how the data is fetched from the cube for reporting)
    I have a query, on a multiprovider connected to cubes say A and B. A is on BIA index, B is not. There are no aggregates created on both the cubes.
    CASE 1: I have taken RSRT stats with BIA on, in aggregation layer it says
    Basic InfoProvider     *****Table type      ***** Viewed at      ***** Records, Selected     *****Records, Transported
    Cube A     ***** blank ***** 0.624305      ***** 8,087,502      ***** 2,011
    Cube B     ***** E ***** 42.002653 ***** 1,669,126      ***** 6
    Cube B     ***** F ***** 98.696442 ***** 2,426,006 ***** 6
    CASE 2:I have taken the RSRT stats, disabling the BIA index, in aggregation layer it says:
    Basic InfoProvider     *****Table Type     *****Viewed at     *****Records, Selected     *****Records, Transported
    Cube B     *****E     *****46.620825     ****1,669,126****     6
    Cube B     *****F     ****106.148337****     2,426,030*****     6
    Cube A     *****E     *****61.939073     *****3,794,113     *****3,499
    Cube A     *****F     ****90.721171****     4,293,420     *****5,584
    now my question is why is here a huge difference in the number of records transported for cube A when compared to case 1. The input criteria for both the cases are the same and the result output is matching. There is no change in the number of records selected for cube A in both cases.It is 8,087,502 in both cases.
    Can someone pls clarify on this difference in records being selected.

    Hi,
    yes, Vitaliy could be guess right. Please check if FEMS compression is enabled (note 1308274).
    What you can do to get more details about the selection is to activate the execurtion plan SQL/BWA queries in data manager. You can also activate the trace functions for BWA in RSRT. So you need to know how both queries select its data.
    Regards,
    Jens

Maybe you are looking for